Cross-site scripting via unbounded DOM nesting
Published Oct 11, 2024 · Updated Nov 3, 2025
Cross-site scripting in DOMPurify before 2.5.0 and 3.0.0 through 3.1.2 allows remote attackers to execute JavaScript via deeply nested HTML. The sanitizer traversal did not track original-tree nesting or node-removal depth, allowing excessive nesting to survive sanitization and mutate into executable markup. Exposure requires an application to sanitize attacker-controlled markup and insert the result into a DOM, where the script runs in that application's origin.
Summary
What happened
Cross-site scripting in DOMPurify before 2.5.0 and 3.0.0 through 3.1.2 allows remote attackers to execute JavaScript via deeply nested HTML. The sanitizer traversal did not track original-tree nesting or node-removal depth, allowing excessive nesting to survive sanitization and mutate into executable markup. Exposure requires an application to sanitize attacker-controlled markup and insert the result into a DOM, where the script runs in that application's origin.
The record
- CVE
- CVE-2024-47875
- Published
- Oct 11, 2024
- Updated
- Nov 3, 2025
- Vendor
- Cure53
- Product
- DOMPurify
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.5.0
- Affected versionversion=< 3.1.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream nesting-based mXSS regression testproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo