CVE-2026-31868: Parse Server vulnerable to stored XSS via file upload of HTML-renderable file types
Impact An attacker can upload a file with a file extension or content type that is not blocked by the default configuration of the Parse Server fileUpload.fileExtensions option. The file can contain malicious code, for example JavaScript in an SVG or XHTML file. When the file is accessed via its URL, the browser renders the file and executes the malicious code in the context of the Parse Server domain.
Published Mar 11, 2026
Affected packages
parse-server
- Ecosystem
- npm
- Affected
- >= 9.0.0-alpha.1, < 9.6.0-alpha.4
- Fixed in
- 9.6.0-alpha.4
- Check
npm ls parse-server
parse-server
- Ecosystem
- npm
- Affected
- < 8.6.30
- Fixed in
- 8.6.30
- Check
npm ls parse-server
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
An attacker can upload a file with a file extension or content type that is not blocked by the default configuration of the Parse Server fileUpload.fileExtensions option. The file can contain malicious code, for example JavaScript in an SVG or XHTML file. When the file is accessed via its URL, the browser renders the file and executes the malicious code in the context of the Parse Server domain. This is a stored Cross-Site Scripting (XSS) vulnerability that can be exploited to steal session tokens, redirect users, or perform actions on behalf of other users.
Affected file extensions and content types include .svgz, .xht, .xml, .xsl, .xslt, and content types application/xhtml+xml and application/xslt+xml for extensionless uploads. Uploading of .html, .htm, .shtml, .xhtml, and .svg files was already blocked.
Patches
The fix adds the missing file extensions and content types to the default value of the fileUpload.fileExtensions server option.
Workarounds
Configure the fileUpload.fileExtensions server option to block the affected file extensions and content types.
References
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-v5hf-f4c3-m5rv
- Fix Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.4
- Fix Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.30
Credited to offset, mtrezza.
References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-v5hf-f4c3-m5rv
- https://github.com/parse-community/parse-server/releases/tag/8.6.30
- https://github.com/parse-community/parse-server/releases/tag/9.6.0-alpha.4
- https://nvd.nist.gov/vuln/detail/CVE-2026-31868
- https://github.com/advisories/GHSA-v5hf-f4c3-m5rv
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-61448
Parse Server vulnerable to stored XSS via malformed Content-Type bypassing file upload extension blocklist
low2.1Oct 29, 2026CVE-2026-50008
parse-server: Server option routeAllowList is bypassable through batch sub-requests
medium6.9Jun 19, 2026CVE-2026-53724
parse-server: Stored XSS via trailing-dot filename bypassing file upload extension blocklist
low2.1Jun 19, 2026CVE-2026-53725
parse-server: Endpoints `/login` and `/verifyPassword` disclose MFA secrets and protected fields when `_User` get is denied
medium5.9Jun 19, 2026CVE-2026-53726
parse-server: Relation `$relatedTo` query bypasses `protectedFields` and owning-object ACL
medium6.9Jun 19, 2026CVE-2026-55778
parse-server: Stored XSS via non-standard file extension bypassing file upload extension blocklist
low2.1Jun 19, 2026
