p PatchFirst

CVE-2026-53724

CVE-2026-53724 · Parse Server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist

This page contains facts from public vulnerability sources. Check the original advisory before updating.

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.79 and 9.9.1-alpha.4, the default file upload extension blocklist can be bypassed by appending a trailing dot to a filename whose extension would otherwise be blocked (e.g. poc.svg.). The trailing dot causes the extension parser to extract an empty string, which short-circuits the blocklist check, and the attacker-controlled Content-Type is forwarded to the storage adapter unchanged. Storage adapters that persist and serve the provided Content-Type (such as S3 or GCS) then serve the file with an active type such as image/svg+xml, enabling stored XSS when a victim opens the file URL. The default GridFS adapter is not affected because it sets X-Content-Type-Options: nosniff on responses. This issue has been patched in versions 8.6.79 and 9.9.1-alpha.4.

CVSS 2.1 · Low · EPSS 0.5% · Fix available

Published
Updated

Stack: node

Affected products and versions

  • parse-server

    Versions
    • < 8.6.79: Affected
    • >= 9.0.0, < 9.9.1-alpha.4: Affected

    No fix published

  • parse-server npm

    Affected ranges
    • SEMVER: ≥ 9.0.0, < 9.9.1-alpha.4

    Update to 9.9.1-alpha.4

  • parse-server npm

    Affected ranges
    • SEMVER: < 8.6.79

    Update to 8.6.79

Original sources

Check your server →