Quick answers
- Is CVE-2026-53724 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53724 being exploited in the wild.
- How severe is CVE-2026-53724?
- Medium severity, with a CVSS score of 4, published 12 June 2026.
- Which products and versions are affected?
- parse-server (npm) SEMVER:introduced=9.0.0,fixed=9.9.1-alpha.4.
- Is there a fix for CVE-2026-53724?
- Yes. parse-server (npm): upgrade to 9.9.1-alpha.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53724 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53724?
- Check whether you run parse-server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- parse-server (npm): upgrade to 9.9.1-alpha.4 or later
npm install parse-server@9.9.1-alpha.4
Technical details
A stored cross-site scripting (XSS) vulnerability exists in Parse Server's file upload handler. The default extension blocklist can be bypassed by appending a trailing dot to a filename (e.g., 'malicious.svg.'). This causes the extension parser to return an empty string, bypassing blocklist checks while preserving the attacker-supplied Content-Type. When stored in adapters like S3 or GCS that serve the original Content-Type, the file is delivered as an active type (e.g., image/svg+xml), executing scripts in the victim's browser. The vulnerability is patched in versions 9.9.1-alpha.4 and 8.6.79.
Affected products
- Parse Community parse-server >= 9.0.0, < 9.9.1-alpha.4; <= 8.6.78
Identifiers
- CVE-2026-53724
- GHSA-7wqv-xjf3-x35v
Timeline
- 2026-06-12: advisory: NVD publication date
- 2026-06-19: disclosed: GitHub Advisory published