Xmldom
xmldom: Attribute name injection via setAttribute() bypasses requireWellFormed
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.14 and 0.9.11, and in xmldom version 0.6.0 and earlier, Element.setAttribute() calls the private _createAttribute(name) path without validating the attribute name, while Document.createAttribute(name) validates against QName. XMLSerializer.serializeToString() emits attribute names verbatim, and requireWellFormed: true did not validate them, so a crafted name can terminate the intended attribute and inject additional attributes, including event handlers, into browser-consumed output; synthesized xmlns:PREFIX declarations expose the same unchecked-name boundary. This issue is fixed in @xmldom/xmldom versions 0.8.14 and 0.9.11; no fixed version is available for xmldom.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- <= 0.6.0
- >= 0.7.0, < 0.8.14
- >= 0.9.0, < 0.9.11
Fixed in 0.8.14, 0.9.11
Mitigation
Upgrade xmldom to 0.8.14 or 0.9.11 or later.
References
- Vendor advisory github.com/xmldom/xmldom/security/advisories/G…
- Patch github.com/xmldom/xmldom/pull/1043
- Patch github.com/xmldom/xmldom/pull/1050
4 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.