DOMPurify contains a Cross-site Scripting vulnerability
Published 3 Mar 2026 · Updated 10 Sept 2026
Affected packages
- Affected
- >=3.1.3 <3.2.7
- Fixed in
- 3.2.7
npm install dompurify@3.2.7- Affected
- >=2.5.3 <=2.5.8
- Fixed in
- No fix released
Details
DOMPurify 3.1.3 through 3.2.6 and 2.5.3 through 2.5.8 contain a cross-site scripting vulnerability that allows attackers to bypass attribute sanitization by exploiting missing textarea rawtext element validation in the SAFE_FOR_XML regex. Attackers can include closing rawtext tags like </textarea> in attribute values to break out of rawtext contexts and execute JavaScript when sanitized output is placed inside rawtext elements. The 3.x branch was fixed in 3.2.7; the 2.x branch was never patched.
Is GHSA-v8jm-5vwx-cfxm in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected dompurify, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-15599
- Linkgithub.com/cure53/DOMPurify/commit/c861f5a83fb8d90800f1680f855fee551161ac2b
- Packagegithub.com/cure53/DOMPurify
- Linkwww.vulncheck.com/advisories/dompurify-xss-via-textarea-rawtext-bypass-in-safe-for-xml
- Linkwww.vulncheck.com/advisories/dompurify-xss-via-textarea-rawtext-bypass-in-safeforxml
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.