Script execution via template-regex sanitizer bypass
Published Feb 14, 2025 · Updated Feb 14, 2025
Mutation cross-site scripting in Cure53 DOMPurify before 3.2.4 allows attackers to execute script through crafted HTML. With SAFE_FOR_TEMPLATES enabled, TMPLIT_EXPR requires a closing brace, so a crafted ${ sequence removes a closing style tag during final string replacement and changes how the browser reparses sanitized markup. Exploitation requires non-default SAFE_FOR_TEMPLATES and custom-element handling, and injected script runs in the consuming application's browser context.
Summary
What happened
Mutation cross-site scripting in Cure53 DOMPurify before 3.2.4 allows attackers to execute script through crafted HTML. With SAFE_FOR_TEMPLATES enabled, TMPLIT_EXPR requires a closing brace, so a crafted ${ sequence removes a closing style tag during final string replacement and changes how the browser reparses sanitized markup. Exploitation requires non-default SAFE_FOR_TEMPLATES and custom-element handling, and injected script runs in the consuming application's browser context.
The record
- CVE
- CVE-2025-26791
- Published
- Feb 14, 2025
- Updated
- Feb 14, 2025
- Vendor
- Cure53
- Product
- DOMPurify
- Classifications
- CWE-79, T1059.007
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2025CVE publishedPublication date reported by the CVE source.
- Feb 14, 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=0 <3.2.4
What conditions does exploitation require?
What is affected?
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
- DOMPurify 3.2.3 Bypass (Non-Default Config)proof 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