{"id":"GHSA-v8x7-r927-cc93","revision":"4efe17f4b8894787a9bba497245ea0eb","records":[{"revision":"4efe17f4b8894787a9bba497245ea0eb","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-v8x7-r927-cc93","aliases":["BIT-parse-2026-55778","CVE-2026-55778"],"title":"parse-server: Stored XSS via non-standard file extension bypassing file upload extension blocklist","description":"### Impact\n\nParse Server's default `fileUpload.fileExtensions` blocklist is intended to prevent uploading files that browsers render as active content (such as HTML and SVG), which can be used to perform stored cross-site scripting (XSS) attacks against other users. The blocklist could be bypassed by uploading a file whose extension is not an exact match of a blocked extension (for example a non-standard or compound extension) together with a dangerous content type. On storage adapters that persist and serve the uploaded content type (such as S3 and GCS), the file is then served with the attacker-supplied content type, enabling stored XSS against users who open the file URL.\n\nThis affects the default configuration, in which authenticated users are allowed to upload files. The default GridFS/filesystem adapter sets the `X-Content-Type-Options: nosniff` response header, which mitigates browser rendering on that adapter, but the upload restriction itself is still bypassed. This is an incomplete-fix follow-up of GHSA-vr5f-2r24-w5hc and GHSA-7wqv-xjf3-x35v.\n\n### Patches\n\nThe file upload extension validation now also evaluates the request content type against the configured blocklist whenever the filename's extension is not a recognized type. As a result, a dangerous content type can no longer be preserved by uploading a file with a non-standard extension, and such uploads are rejected.\n\n### Workarounds\n\nConfigure `fileUpload.fileExtensions` as a strict allowlist of only the file extensions your application needs (for example `[\"^(png|jpe?g|gif|pdf)$\"]`) instead of relying on the default blocklist. Additionally, serve uploaded files from a separate domain than the application, so that any executed content is isolated from the application's origin.","state":0,"publishedAt":"2026-06-19T19:36:36+00:00","modifiedAt":"2026-07-14T16:40:35.6299926+00:00","affected":[{"ecosystem":"npm","name":"parse-server","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"9.0.0"},{"kind":"fixed","version":"9.9.1-alpha.11"}]}],"versions":[],"rawVersionEvidence":null},{"ecosystem":"npm","name":"parse-server","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"8.6.81"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V4","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"LOW"}],"references":["https://github.com/parse-community/parse-server/security/advisories/GHSA-v8x7-r927-cc93","https://github.com/parse-community/parse-server/pull/10505","https://github.com/parse-community/parse-server/pull/10506","https://github.com/parse-community/parse-server"],"sourceUrl":"https://github.com/advisories/GHSA-v8x7-r927-cc93","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-v8x7-r927-cc93","identifiers":["GHSA-v8x7-r927-cc93","BIT-parse-2026-55778","CVE-2026-55778"]},"retained":false,"historicalAffected":[]}],"coverage":[]}