xmldom: Element name injection via createElement() bypasses requireWellFormed
xmldom · @xmldom xmldom
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @xmldom/xmldom npm |
|
|
| xmldom npm |
| No fix yet |
xmldom · @xmldom xmldom
| Product | Affected | Fixed in |
|---|---|---|
| @xmldom/xmldom npm |
|
|
| xmldom npm |
| No fix yet |
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.
From the CVE record · GitHub_M
Affected xmldom packages do not validate attacker-controlled element names passed to Document.createElement() before XMLSerializer.serializeToString() emits them, including with requireWellFormed: true. An attacker who controls a tag name can inject attributes, elements, or processing instructions into serialized XML or HTML; this can cause cross-site scripting if a browser consumes the output.
Check applications using npm @xmldom/xmldom versions >=0.7.0 <0.8.14 or >=0.9.0 <0.9.11, or npm xmldom version 0.6.0 or earlier.