CVE-2026-30948: parse-server · Cross-site Scripting
Affects parse-serverSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 9.5.2-alpha.4 or 8.6.17 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.5.2-alpha.4, 8.6.17
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade parse-server to 9.5.2-alpha.4 or 8.6.17; parse-server to 8.6.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| parse-communityparse-server | Affected
| Fixed in
|
| parse-communityparse-server | Affected
| Fixed in
|
npmparse-serverpkg:npm/parse-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should immediately upgrade parse-server to version 9.5.2-alpha.4, 8.6.17, or later where the vulnerability is patched. Until upgrades can be applied, administrators should disable file uploads for authenticated users or restrict allowed file types to exclude SVG files. Implementing strict Content Security Policy (CSP) headers that disallow inline scripts and restrict script sources can mitigate exploitation risk. Additionally, configuring the server to serve SVG files with the Content-Disposition header set to attachment rather than inline can prevent automatic script execution. Employing X-Content-Type-Options: nosniff headers can also reduce risk by preventing MIME type sniffing. Regularly auditing file upload functionality and monitoring logs for suspicious SVG uploads is recommended. Developers should review and harden file validation logic to reject potentially dangerous file types and sanitize all user-supplied content. Finally, educating users about the risks of clicking on untrusted links or files within the application can reduce the likelihood of successful exploitation.
Description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.5.2-alpha.4 and 8.6.17, a stored cross-site scripting (XSS) vulnerability allows any authenticated user to upload an SVG file containing JavaScript. The file is served inline with Content-Type: image/svg+xml and without protective headers, causing the browser to execute embedded scripts in the Parse Server origin. This can be exploited to steal session tokens from localStorage and achieve account takeover. The default fileExtensions option blocks HTML file extensions but does not block SVG, which is a well-known XSS vector. All Parse Server deployments where file upload is enabled for authenticated users (the default) are affected. This vulnerability is fixed in 9.5.2-alpha.4 and 8.6.17.