Summary
xhtml-purifier has HTML attribute-injection (sanitizer bypass) that leads to XSS
Advisory details
xhtml-purifier does not HTML-entity-encode attribute values when serializing its sanitized output. In attributeString() (XHTMLPurifier.js, around line 148) the attribute value is concatenated directly into a double-quoted attribute without encoding. As a result, an attacker-controlled value in any allowed attribute (class, style, title, alt, src, href) can include a double-quote character to break out of the attribute and inject an additional attribute, such as a JavaScript event handler (for example onmouseover or onerror). The injected handler survives sanitization and executes when the output is rendered, which is a sanitizer bypass leading to cross-site scripting. The fix HTML-entity-encodes attribute values before serialization.
References
- https://github.com/advisories/GHSA-j8r4-32c5-33rc
- https://github.com/cstigler/node-xhtml-purifier/security/advisories/GHSA-j8r4-32c5-33rc
- https://nvd.nist.gov/vuln/detail/CVE-2026-61784
- https://github.com/cstigler/node-xhtml-purifier/pull/6
- https://github.com/cstigler/node-xhtml-purifier/commit/21d461ad23e7bc9b3073693d5b51b9b8662044d3
- https://github.com/cstigler/node-xhtml-purifier/releases/tag/v0.4.3
Related vulnerabilities
All Supply chain →- CRITICALCVE-2026-104252
Vitess vttablet /twopcz reflected XSS
- MEDIUMCVE-2026-104250
unstructured: Stored XSS via unescaped HTML generation
- CRITICALCVE-2026-107845
Contao: Cross-site scripting in the comments bundle
- HIGHCVE-2026-106107
Quasar Framework: App Vite SSR and SSG nonce attributes are not safely constrained
- CRITICALCVE-2026-106102
Quasar Framework: Stored/Reflected XSS via unescaped SSR meta tag rendering in getHead()
- HIGHGHSA-g2v6-rqmx-r4w6
@vue/server-renderer: XSS via missing CR in attribute-name blacklist