Is this vulnerability remotely exploitable?

It can be, if a remote party can supply or influence data that your application inserts into CDATASection nodes and then serializes. In such scenarios, a remote attacker may inject XML structure into the resulting documents.

What level of access does an attacker need to exploit this issue?

The attacker needs control over the content that becomes part of a CDATASection, which can occur through typical user inputs, API parameters, or external data feeds that the application embeds into XML before serialization.

What is the safest general fix pattern?

Ensure that any data placed into CDATASection nodes is either validated to disallow the `]]>` sequence or processed by a serializer that automatically escapes or splits CDATA content containing terminators. The general pattern is to never emit untrusted data as raw XML without robust escaping or structure-aware handling.

Severity:

HIGH RISK

(7.5)

XML Injection via Unsanitized CDATA Terminator (CWE-91) in xmldom DOMParser/XMLSerializer

CVE-2026-34601

Published:

Apr 2, 2026

Status:

Deferred

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-94

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

Remote Code Execution by authenticated users via malicious file upload

May 10, 2026

CWE-94

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Remote Code Execution by Authenticated Users

May 10, 2026

Vulnerability Type

Category:

XML Injection

CWE:

CWE-91

Impact:

XML Structure Injection and Business Logic Manipulation

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

XML Injection

CWE:

CWE-91

Impact:

XML Structure Injection and Business Logic Manipulation

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest that knows every line of it.

Ask AI for summary of CodeAnt

XML Injection via Unsanitized CDATA Terminator (CWE-91) in xmldom DOMParser/XMLSerializer

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.8)

PHP Code Injection via File Upload (CWE-94) in Aero CMS Admin Post Creation

HIGH RISK

HIGH

(8.8)

Code Injection (CWE-94) via Module Parameters in Evolution CMS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal