Xmldom
xmldom: DocType `name` Injection 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.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, the DOCUMENT_TYPE_NODE branch in lib/dom.js validates publicId, systemId, and internalSubset under requireWellFormed: true but emits DocumentType.name verbatim. A name containing > or whitespace can terminate the <!DOCTYPE ...> declaration and inject sibling markup; the value can be supplied through createDocumentType() on the 0.8.x and unscoped lines or through a direct DocumentType.name property write on every affected line. The default path and legacy creation-time behavior remain permissive, while the vulnerable strict path fails to enforce an XML Name. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; 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.9.0, < 0.9.12
- >= 0.7.0, < 0.8.15
Fixed in 0.9.12, 0.8.15
Mitigation
Upgrade xmldom to 0.9.12 or 0.8.15 or later.
References
- Vendor advisory github.com/xmldom/xmldom/security/advisories/G…
- Patch github.com/xmldom/xmldom/pull/1071
- Patch github.com/xmldom/xmldom/pull/1072
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.