DOMPurify before 3.4.11 fails to clone the ALLOWED_ATTR allowlist when setConfig() is used with an uponSanitizeAttribute hook, allowing the hook to permanently mutate the shared allowlist. Attackers can register a hook that conditionally allows dangerous attributes like onerror for trusted elements, then submit untrusted content that inherits the polluted allowlist and executes event handlers as stored XSS.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 5.1 · cure53NVD modified 2026-10-24 13:10
Affected (CPE criteria) 1
cpe:2.3:a:cure53:dompurify:*:*:*:*:*:*:*:*
References 3
- https://github.com/cure53/DOMPurify/security/advisories/GHSA-cmwh-pvxp-8882 Exploit, Third Party Advisory
- https://www.vulncheck.com/advisories/dompurify-before-permanent-attribute-allowlist-pollution-via-setconfig Third Party Advisory
- https://github.com/cure53/DOMPurify/security/advisories/GHSA-cmwh-pvxp-8882 Exploit, Third Party Advisory