Parse Server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist

Summary

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.

Timeline

1. Jun 12, 2026, 6:34 PM UTCCVE published
2. Jun 12, 2026, 7:03 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Jun 12, 2026, 8:01 PM UTCRecord last updated

Affected versions

• parse-community parse-server

  fixed in 8.6.79; From 9.0.0 · fixed in 9.9.1-alpha.4

• parse-servernpm

  From 9.0.0 · fixed in 9.9.1-alpha.4

• parse-servernpm

  fixed in 8.6.79

References 3