DOMPurify from 3.4.4 before 3.4.17 SAFE_FOR_TEMPLATES Bypass via Shadow Root Content
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.4.17
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
DOMPurify, a JavaScript library used to sanitize HTML in web applications, is affected by a flaw that can let malicious template expressions survive sanitization when certain output modes are used. This could allow attackers to run cross-site scripting attacks if the sanitized output is later processed by a template engine.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
DOMPurify from 3.4.4 before 3.4.17 contains a SAFE_FOR_TEMPLATES bypass that lets attackers preserve template expressions in attached shadow roots when using RETURN_DOM, RETURN_DOM_FRAGMENT, or IN_PLACE modes. Attackers can split expressions across text nodes separated by disallowed elements, which merge after removal and are evaluated by downstream template engines for cross-site scripting.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- cure53 DOMPurify
From 3.4.4 · fixed in 3.4.17
- dompurifynpm
From 3.4.4 · fixed in 3.4.17