The vulnerability allows an attacker to inject characters - such as quotes and spaces - into the attribute name parameter of setAttribute(), effectively terminating the intended attribute and injecting new ones (e.g., onclick event handlers) into the document tree. Because the library's XMLSerializer performs no validation by default, these injected attributes are rendered verbatim in the output. If this output is subsequently parsed by a browser, it can result in Cross-Site Scripting (XSS) or the overriding of security-critical attributes like integrity or Content-Security-Policy. This vulnerability affects versions of @xmldom/xmldom from 0.7.0 through 0.9.10, as well as the legacy xmldom package (<= 0.6.0).

Impact

Successful exploitation allows for arbitrary attribute injection when user-supplied input is reflected in attribute names. This poses a significant risk to web applications using this library to process or generate XML/HTML, as it can lead to XSS, bypass of security constraints, or unauthorized execution of JavaScript if the resulting XML is rendered as HTML in a browser context.

Recommendation

• Upgrade to @xmldom/xmldom version 0.9.11 or 0.8.14 or later to access the new validation features.
• Implement the requireWellFormed: true option in all XMLSerializer.serializeToString() calls that process untrusted or partially user-controlled DOM content.
• Perform an audit of the codebase to identify all locations where user-provided strings are passed as the 'name' parameter to setAttribute().
• Validate all attribute names against the XML QName production before calling setAttribute() if the library cannot be updated or if strict serialization cannot be enabled.