Dompurify vulnerabilitiesRanked by how likely they are to be used.
Dompurify is made by Cure53. We track 7 published vulnerabilities in it, across 114 versions. None of them is on the list of flaws known to be exploited today. If you run Dompurify, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Dompurify vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Dompurify's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Dompurify flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 4.9%CVE-2020-26870Medium
Cure53 DOMPurify before 2.0.17 allows mutation XSS.
- 1.7%CVE-2019-16728Medium
DOMPurify before 2.0.1 allows XSS because of innerHTML mutation XSS (mXSS) for an SVG element or a MATH element, as demonstrated by Chrome and Safari.
- 1.2%CVE-2024-48910Critical
DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG.
- 1.1%CVE-2024-47875Critical
DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG.
- 0.9%CVE-2024-45801High
DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG.
- 0.6%CVE-2025-26791Medium
DOMPurify before 3.2.4 has an incorrect template literal regular expression, sometimes leading to mutation cross-site scripting (mXSS).
- 0.5%CVE-2019-25155Medium
DOMPurify before 1.0.11 allows reverse tabnabbing in demos/hooks-target-blank-demo.html because links lack a 'rel="noopener noreferrer"' attribute.
- 0.4%CVE-2026-65899Medium
DOMPurify 3.0.0 before 3.4.9 does not reset the retained Trusted Types policy when clearConfig() is called, so a DOMPurify instance reused across trust boundaries stays bound to a previously supplied TRUSTED_TYPES_POLICY.
- 0.3%CVE-2026-65913Medium
DOMPurify before 3.3.2 contains a prototype pollution vulnerability in USE_PROFILES mode that allows attackers to bypass attribute filtering by polluting Array.prototype properties.
- 0.2%CVE-2025-15599Medium
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...
Running Dompurify? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Cure53 DOMPurify before 2.0.17 allows mutation XSS. This occurs because a serialize-parse roundtrip does not necessarily return the original DOM tree, and a namespace can change from HTML to MathML, as demonstrated by nesting of FORM elements.
- Matched to
- Dompurify on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 7 published vulnerabilities listed under the name Dompurify, across 114 versions.
None of Dompurify's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Dompurify. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.