CWE-112: Missing XML Validation

Code Examples & CVEs

Demonstrative Examples

The following code loads and parses an XML file.

The XML file is loaded without validating it against a known XML Schema or DTD.

BadJava

// Read DOM                      try {...DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();factory.setValidating( false );....c_dom = factory.newDocumentBuilder().parse( xmlFile );} catch(Exception ex) {...}

The following code creates a DocumentBuilder object to be used in building an XML document.

The DocumentBuilder object does not validate an XML document against a schema, making it possible to create an invalid XML document.

BadJava

DocumentBuilderFactory builderFactory = DocumentBuilderFactory.newInstance();builderFactory.setNamespaceAware(true);DocumentBuilder builder = builderFactory.newDocumentBuilder();

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-112 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-112, Missing XML Validation, 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 Missing XML Validation

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

CWE-112: Missing XML Validation — MITRE CWE

Triage CWE-112 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-112, Missing XML Validation, 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-112

Apply MITRE's full root-cause mapping guidance when using CWE-112, Missing XML Validation. 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-112 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-112, Missing XML Validation. 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-112: Missing XML Validation?+

CWE-112: Missing XML Validation is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product accepts XML from an untrusted source but does not validate the XML against the proper schema. Most successful attacks begin with a violation of the programmer's assumptions. By accepting an XML document without validating it against a DTD or XML schema, the programmer leaves a door open for attackers to provide unexpected, unreasonable, or malicious input.

What are the security consequences of Missing XML Validation?+

If exploited, CWE-112 (Missing XML Validation) it can compromise Integrity, leading to outcomes such as Unexpected State.

How do you prevent or mitigate Missing XML Validation?+

Recommended mitigations for CWE-112 include: Always validate XML input against a known XML Schema or DTD. It is not possible for an XML parser to validate all aspects of a document's content because a parser cannot understand the complete semantics of the data. However, a parser can do a complete and thorough job of checking the document's structure and therefore guarantee to the code that processes the document that the content is well-formed.

Which programming languages are affected by Missing XML Validation?+

CWE-112 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-112 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-112: Missing XML Validation

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Strategy

Detection Methods