xmldom: Attribute name injection via setAttribute() bypasses requireWellFormed
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.7epss 0.3%
exploitation probability
0.3%top 72% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
References
https://github.com/xmldom/xmldom/commit/cba1321218b069182695813fa7565653708e172ehttps://github.com/xmldom/xmldom/commit/d8212e632507eaf1d9f609657dd4c56abeb12d44https://github.com/xmldom/xmldom/pull/1043https://github.com/xmldom/xmldom/pull/1050https://github.com/xmldom/xmldom/releases/tag/0.8.14https://github.com/xmldom/xmldom/releases/tag/0.9.11https://github.com/xmldom/xmldom/security/advisories/GHSA-4w3w-2rp5-g8jm