CVE-2026-32728: Parse server Cross-Site Scripting Vulnerability

HIGH
Advisory Identifier: GHSA-42ph-pf9q-cr72
CWE-79
Published
Advisory Summary

CVE-2026-32728 is a HIGH cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Parse server libraries in the npm ecosystem. The issue involves parse server has a stored xss filter bypass via content-type mime parameter and missing xml extension blocklist entries. Remediation is available by upgrading affected packages to version 9.6.0-alpha.15, 8.6.41.

CVE-2026-32728 at a Glance

CVE Identifier CVE-2026-32728
GHSA Identifier GHSA-42ph-pf9q-cr72
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product Parse server
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-32728

To remediate this vulnerability, upgrade all affected Parse server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

parse-server fixed: 9.6.0-alpha.15
npm install parse-server@9.6.0-alpha.15
parse-server fixed: 8.6.41
npm install parse-server@8.6.41
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls parse-server

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-32728, inspect your project dependencies using npm:

npm ls parse-server

Analyze the terminal output to locate any version of Parse server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 9.6.0-alpha.15), your application is affected.

Note: The npm ls parse-server command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Parse server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact An attacker who is allowed to upload files can bypass the file extension filter by appending a MIME parameter (e.g. `;charset=utf-8`) to the `Content-Type` header. This causes the extension validation to fail matching against the blocklist, allowing active content to be stored and served under the application's domain. In addition, certain XML-based file extensions that can render scripts in web browsers are not included in the default blocklist. This can lead to stored XSS attacks, compromising session tokens, user credentials, or other sensitive data accessible via the browser's local storage. ### Patches The fix strips MIME parameters from the `Content-Type` header before validating the file extension against the blocklist. The default blocklist has also been extended to include additional XML-based extensions (`xsd`, `rng`, `rdf`, `rdf+xml`, `owl`, `mathml`, `mathml+xml`) that can render active content in web browsers. Note that the `fileUpload.fileExtensions` option is intended to be configured as an allowlist of file extensions that are valid for a specific application, not as a denylist. The default denylist is provided only as a basic default that covers most common problematic extensions. It is not intended to be an exhaustive list of all potentially dangerous extensions. Developers should not rely on the default value, as new extensions that can render active content in browsers might emerge in the future. ### Workarounds Configure the `fileUpload.fileExtensions` option to use an allowlist of only the file extensions that your application needs, rather than relying on the default blocklist.

CVE-2026-32728 Affected Parse server Versions

2 component(s)
Fixed Versions:
9.6.0-alpha.158.6.41
Product / Package Ecosystem Affected Versions Fixed Version
parse-server
npm
≥ 9.0.0
< 9.6.0-alpha.15
9.6.0-alpha.15
parse-server
npm
< 8.6.41
8.6.41

References

Frequently Asked Questions

What is CVE-2026-32728?
CVE-2026-32728 is a security vulnerability in Parse server involving Parse Server has a stored XSS filter bypass via Content-Type MIME parameter and missing XML extension blocklist entries under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which Parse server versions are affected?
Affected versions include releases prior to 9.6.0-alpha.15, 8.6.41 across affected packages: parse-server.
What version fixes CVE-2026-32728?
Upgrading to 9.6.0-alpha.15, 8.6.41 (or the latest patched release for your respective branch) resolves the vulnerability.
Is parse-server affected?
Yes, parse-server is affected in releases prior to 9.6.0-alpha.15, 8.6.41. Upgrade your dependency to 9.6.0-alpha.15, 8.6.41 or later.
What CWE is associated with CVE-2026-32728?
CVE-2026-32728 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check npm dependencies for CVE-2026-32728?
Run the dependency tree command: 'npm ls parse-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-42ph-pf9q-cr72",
  "modified" : "2026-03-19T21:11:36Z",
  "published" : "2026-03-16T18:46:00Z",
  "aliases" : [ "CVE-2026-32728" ],
  "summary" : "Parse Server has a stored XSS filter bypass via Content-Type MIME parameter and missing XML extension blocklist entries",
  "details" : "### Impact\n\nAn attacker who is allowed to upload files can bypass the file extension filter by appending a MIME parameter (e.g. `;charset=utf-8`) to the `Content-Type` header. This causes the extension validation to fail matching against the blocklist, allowing active content to be stored and served under the application's domain. In addition, certain XML-based file extensions that can render scripts in web browsers are not included in the default blocklist.\n\nThis can lead to stored XSS attacks, compromising session tokens, user credentials, or other sensitive data accessible via the browser's local storage.\n\n### Patches\n\nThe fix strips MIME parameters from the `Content-Type` header before validating the file extension against the blocklist. The default blocklist has also been extended to include additional XML-based extensions (`xsd`, `rng`, `rdf`, `rdf+xml`, `owl`, `mathml`, `mathml+xml`) that can render active content in web browsers.\n\nNote that the `fileUpload.fileExtensions` option is intended to be configured as an allowlist of file extensions that are valid for a specific application, not as a denylist. The default denylist is provided only as a basic default that covers most common problematic extensions. It is not intended to be an exhaustive list of all potentially dangerous extensions. Developers should not rely on the default value, as new extensions that can render active content in browsers might emerge in the future.\n\n### Workarounds\n\nConfigure the `fileUpload.fileExtensions` option to use an allowlist of only the file extensions that your application needs, rather than relying on the default blocklist.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.0.0"
      }, {
        "fixed" : "9.6.0-alpha.15"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "parse-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "8.6.41"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/security/advisories/GHSA-42ph-pf9q-cr72"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32728"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10191"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/pull/10192"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/commit/4f53ab3cad5502a51a509d53f999e00ff7217b8d"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/parse-community/parse-server/commit/c7599c577a02b97eb5e76d4e20517b0283ae73c8"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/parse-community/parse-server"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-16T18:46:00Z",
    "nvd_published_at" : "2026-03-18T22:16:24Z"
  }
}