xmldom: XML injection via unsafe CDATA serialization allows attacker-controlled markup insertion
xmldom
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| xmldom npm |
| No fix yet |
| @xmldom/xmldom npm |
|
|
xmldom
| Product | Affected | Fixed in |
|---|---|---|
| xmldom npm |
| No fix yet |
| @xmldom/xmldom npm |
|
|
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) `DOMParser` and `XMLSerializer` module. In xmldom versions 0.6.0 and prior and @xmldom/xmldom prior to versions 0.8.12 and 0.9.9, xmldom/xmldom allows attacker-controlled strings containing the CDATA terminator ]]> to be inserted into a CDATASection node. During serialization, XMLSerializer emitted the CDATA content verbatim without rejecting or safely splitting the terminator. As a result, data intended to remain text-only became active XML markup in the serialized output, enabling XML structure injection and downstream business-logic manipulation. This issue has been patched in xmldom version 0.6.0 and @xmldom/xmldom versions 0.8.12 and 0.9.9.
From the CVE record · GitHub_M
Affected xmldom packages serialize CDATA content containing `]]>` without rejecting or safely splitting it. If an attacker can control text inserted into a CDATASection, they can turn text-only data into XML markup and potentially manipulate downstream business logic. The input does not specify network access, authentication requirements, or user interaction.
Check applications using npm xmldom versions 0.6.0 and earlier or npm @xmldom/xmldom versions before 0.8.12 or from 0.9.0 through 0.9.8.