xmldom: Element name injection via createElement() 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, Document.createElement(tagName) stores an unvalidated element name and XMLSerializer.serializeToString() emits that name verbatim. The requireWellFormed: true path did not validate the element qualified name or synthesized xmlns:PREFIX declaration, so attacker-controlled tag names could inject attributes, elements, or processing instructions into serialized XML or HTML and could cause cross-site scripting when browser-consumed. The unchecked values violate the XML QName constraint, and default serialization and creation-time createElement() behavior remain permissive. 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-w2rr-34g9-rvrj