Advisory

GHSA-v5hf-f4c3-m5rv

Also known as: BIT-parse-2026-31868, CVE-2026-31868

Summary

Parse Server vulnerable to stored XSS via file upload of HTML-renderable file types

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-03-11 00:34 UTC
Modified
2026-03-13 13:11 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 9.0.0-alpha.1, fixed 9.6.0-alpha.4 (semver)

Fixed versions

9.6.0-alpha.4

Fix

parse-server

npm · All systems

Affected

  • introduced 0, fixed 8.6.30 (semver)

Fixed versions

8.6.30

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences