How severe is GHSA-42ph-pf9q-cr72?

No CVSS score has been assigned to GHSA-42ph-pf9q-cr72 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-42ph-pf9q-cr72?

GHSA-42ph-pf9q-cr72 affects the following packages: parse-server (npm), parse-server (npm). Ecosystems affected: npm.

How do I fix GHSA-42ph-pf9q-cr72?

Update parse-server to 9.6.0-alpha.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-42ph-pf9q-cr72 is resolved across your whole dependency graph.

How do I detect GHSA-42ph-pf9q-cr72 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for parse-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-42ph-pf9q-cr72 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-42ph-pf9q-cr72 actively exploited in the wild?

No public exploit code has been indexed for GHSA-42ph-pf9q-cr72 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-42ph-pf9q-cr72?

GHSA-42ph-pf9q-cr72 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 22th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-42ph-pf9q-cr72?

GHSA-42ph-pf9q-cr72 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-42ph-pf9q-cr72 published, and has it been updated?

GHSA-42ph-pf9q-cr72 was published on March 16, 2026 and was last updated on March 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Parse Server has a stored XSS filter bypass via Content-Type MIME parameter and missing XML extension blocklist entriesGHSA-42ph-pf9q-cr72

Fix: parse-community/parse-server#10191

GHSA-42ph-pf9q-cr72 is a Cross-site Scripting (XSS) vulnerability in parse-server. A fix is available for parse-server — see the affected versions and patch details below.

Also known asBIT-parse-2026-32728CVE-2026-32728

Published

Mar 16, 2026

Updated

Mar 20, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-42ph-pf9q-cr72.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs22th percentile — riskier than 22% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

62other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

parse-servernpm

65Kdownloads / week

Description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.15 and 8.6.41, 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. The fix in versions 9.6.0-alpha.15 and 8.6.41 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. As a workaround, 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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`parse-server`	≥ 9.0.0&&< 9.6.0-alpha.15	9.6.0-alpha.15`npm install parse-server@9.6.0-alpha.15`
📦npm	`parse-server`	all versions	8.6.41`npm install parse-server@8.6.41`

Affected Products

1 product · 16 configurations

Application

parse-serverparseplatform

≥ 9.0.0 && < 9.6.0

1 version

9.6.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for parse-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update parse-server to 9.6.0-alpha.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-42ph-pf9q-cr72 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-42ph-pf9q-cr72 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works