Stored XSS via persistent attribute allowlist pollution
Published Jul 23, 2026 · Updated Jul 23, 2026
Cross-site scripting in Cure53 DOMPurify before 3.4.11 allows remote attackers to execute script via sanitized HTML. The setConfig() path skips the _parseConfig clone guard, so an uponSanitizeAttribute hook receives the shared ALLOWED_ATTR object and permanently adds attributes that later untrusted input retains. Exploitation requires persistent configuration, a hook that conditionally adds an unsafe attribute, and a prior trusted render; later stored content executes in viewers' browsers.
Summary
What happened
Cross-site scripting in Cure53 DOMPurify before 3.4.11 allows remote attackers to execute script via sanitized HTML. The setConfig() path skips the _parseConfig clone guard, so an uponSanitizeAttribute hook receives the shared ALLOWED_ATTR object and permanently adds attributes that later untrusted input retains. Exploitation requires persistent configuration, a hook that conditionally adds an unsafe attribute, and a prior trusted render; later stored content executes in viewers' browsers.
The record
- CVE
- CVE-2026-65898
- Published
- Jul 23, 2026
- Updated
- Jul 23, 2026
- Vendor
- Cure53
- Product
- DOMPurify
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 23, 2026CVE publishedPublication date reported by the CVE source.
- Jul 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.4.11
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-cmwh-pvxp-8882 Node and browser proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo