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.
References
| Link | Resource |
|---|---|
| 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 |
Configurations
History
No history.
Information
Published : 2026-07-23 14:18
Updated : 2026-07-28 15:54
NVD link : CVE-2026-65898
Mitre link : CVE-2026-65898
CVE.ORG link : CVE-2026-65898
JSON object : View
Products Affected
cure53
- dompurify
CWE
CWE-79
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
