Skip to main content
VulnerabilityPublished Updated

CVE-2024-48910: DOMPurify vulnerable to tampering by prototype polution

Affects dompurifySource GCVE Database

0
Compare
Authoritative record:CVE-2024-48910· Critical 9.1

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

Data as of 30 Oct 2026, 00:41 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.19.1
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. Weaponized: 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 29 Oct 2026.

What to do

Upgrade dompurify to 2.4.2.

Affected software

ProductAffectedFixed in
npmdompurifyAffected
  • <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

Upgrade DOMPurify to version 2.4.2 or later, where this prototype pollution vulnerability has been fixed. No other mitigation is necessary as the patch fully addresses the issue.

Description

DOMPurify versions prior to 2.4.2 are vulnerable to prototype pollution, which could allow an attacker to tamper with the prototype of base objects. This vulnerability has been assigned CVE-2024-48910 and is rated critical with a CVSS score of 9.1. The issue was fixed in version 2.4.2.

References

Community reviews

Loading reviews…