CWE-91: XML Injection (aka Blind XPath Injection)

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-91 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-91, XML Injection (aka Blind XPath Injection), throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Apply Input Validation controls for XML Injection (aka Blind XPath Injection)

MITRE associates mitigation with Implementation; the listed strategies include Input Validation; documented detection approaches include Automated Static Analysis. Use these source-defined anchors to turn CWE-91 into implementation, review, and verification checks for the affected component.

CWE-91: XML Injection (aka Blind XPath Injection) — MITRE CWE

Triage CWE-91 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-91, XML Injection (aka Blind XPath Injection), has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-91

Apply MITRE's full root-cause mapping guidance when using CWE-91, XML Injection (aka Blind XPath Injection). Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-91 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-91, XML Injection (aka Blind XPath Injection). Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-91: XML Injection (aka Blind XPath Injection)?+

CWE-91: XML Injection (aka Blind XPath Injection) is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system. Within XML, special elements could include reserved words or characters such as "<", ">", """, and "&", which could then be used to add new data or modify XML syntax.

What are the security consequences of XML Injection (aka Blind XPath Injection)?+

If exploited, CWE-91 (XML Injection (aka Blind XPath Injection)) it can compromise Confidentiality, Integrity and Availability, leading to outcomes such as Execute Unauthorized Code or Commands, Read Application Data and Modify Application Data.

Which programming languages are affected by XML Injection (aka Blind XPath Injection)?+

CWE-91 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-91 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-91: XML Injection (aka Blind XPath Injection)

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Detection Methods

Code Examples & CVEs

CWE Relationships

Parent Weaknesses