DOMPurify through 3.3.3 fails to sanitize DOM elements passed via IN_PLACE mode when the element originates from a different window/realm (e.g., an iframe's contentDocument). A cross-realm instanceof check in the private _isNode() function returns false for foreign-realm nodes, causing DOMPurify to stringify the element (yielding '[object HTMLDivElement]'), silently reset IN_PLACE to false, and return the unsanitized element unchanged with any XSS payloads intact.
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 2.3 · 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-4w3q-35jp-p934 Exploit, Third Party Advisory
- https://www.vulncheck.com/advisories/dompurify-before-cross-site-scripting-via-in-place-mode Third Party Advisory
- https://github.com/cure53/DOMPurify/security/advisories/GHSA-4w3q-35jp-p934 Exploit, Third Party Advisory