DOMPurify XSS via Missing Rawtext Elements in SAFE_FOR_XML
Historical advisory recorded 23 Oct 2026 15:48:27 UTC. Read the latest advisory.
cve-program · CVE-2026-0540
PublishedDOMPurify 3.1.3 through 3.3.1 and 2.5.3 through 2.5.8, fixed in commit 2726c74, contain a cross-site scripting vulnerability that allows attackers to bypass attribute sanitization by exploiting five missing rawtext elements (noscript, xmp, noembed, noframes, iframe) in the SAFE_FOR_XML regex. Attackers can include payloads like </noscript><img src=x onerror=alert(1)> in attribute values to execute JavaScript when sanitized output is placed inside these unprotected rawtext contexts.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-0540 · CVE overview and exploitation status
cve-program · CVE-2026-0540
- https://github.com/cure53/DOMPurify
- https://github.com/cure53/DOMPurify/commit/302b51de22535cc90235472c52e3401bedd46f80
- https://github.com/cure53/DOMPurify/releases/tag/3.3.2
- https://fluidattacks.com/advisories/daft
- https://www.vulncheck.com/advisories/dompurify-xss-via-missing-rawtext-elements-in-safe-for-xml
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.