CVE-2020-26870: Cure53 Dompurify vulnerability
Cure53 · Dompurify
Fixed in 2.0.17 · Affected: Cure53 Dompurify before 2.0.17 · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 92% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
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.
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Cross-site Scripting
- Vendor
- Cure53
- Published
- October 2020
CoverageNo articles yet
No CyberSIXT article names CVE-2020-26870 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-79cwe.mitre.org
- Vendor advisoryportal.msrc.microsoft.com
- research.securitum.com/mutation-xss-via-mathml-mutation-dompurifresearch.securitum.com
- github.com/cure53/DOMPurify/commit/02724b8eb048dd219d6725b05c300github.com
- github.com/cure53/DOMPurify/compare/2.0.16...2.0.17github.com
- oracle.com//security-alerts/cpujul2021.htmloracle.com
- Mailing listlists.debian.org