Skip to main content
CVE-2024-48910VulnerabilityPublished Updated

CVE-2024-48910: cure53 DOMPurify · Prototype Pollution

Affects cure53 DOMPurifySource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical : upgrade to 2.4.2 as a priority.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade cure53 DOMPurify to 2.4.2.

Affected software

ProductAffectedFixed in
npmdompurifypkg:npm/dompurifyOther threatsAffected
  • <2.4.2
Fixed in
  • 2.4.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately upgrade all instances of DOMPurify to version 2.4.2 or later to apply the official patch addressing the prototype pollution vulnerability. 2. Conduct a thorough audit of all web applications utilizing DOMPurify to identify and remediate unsafe usage patterns, such as unsanitized inputs or improper integration. 3. Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks. 4. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with rules tuned to detect and block prototype pollution and related injection attempts. 5. Monitor application logs and network traffic for unusual behavior indicative of exploitation attempts, focusing on anomalous object property modifications. 6. Educate development teams on secure coding practices related to prototype pollution and sanitization libraries. 7. Establish a rapid patch management process to respond promptly to future vulnerabilities in third-party libraries. 8. Consider isolating critical web application components to limit the blast radius in case of compromise.

Description

DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. DOMPurify was vulnerable to prototype pollution. This vulnerability is fixed in 2.4.2.

References

Community reviews

Loading reviews…