An attacker utilizes crafted XML user-controllable input to probe, attack, and inject data into the XML database, using techniques similar to SQL injection. The user-controllable input can allow for unauthorized viewing of data, bypassing authentication or the front-end application for direct XML database access, and possibly altering database information.
High

1
Explore
[Survey the Target] Using a browser or an automated tool, an adversary records all instances of user-controllable input used to contruct XML queries
Use an automated tool to record all instances of user-controllable input used to contruct XML queries.
Use a browser to manually explore the website and analyze how the application processes inputs.

2
Experiment
[Determine the Structure of Queries] Using manual or automated means, test inputs found for XML weaknesses.
Use XML reserved characters or words, possibly with other input data to attempt to cause unexpected results and identify improper input validation.

3
Exploit
[Inject Content into XML Queries] Craft malicious content containing XML expressions that is not validated by the application and is executed as part of the XML queries.
Use the crafted input to execute unexpected queries that can disclose sensitive database information to the attacker.

XML queries used to process user input and retrieve information stored in XML documents
User-controllable input not properly sanitized

An attacker must have knowledge of XML syntax and constructs in order to successfully leverage XML Injection

None: No specialized resources are required to execute this type of attack.

Too many exceptions generated by the application as a result of malformed queries

Confidentiality
Access Control
Authorization
Gain Privileges

Confidentiality
Read Data

Strong input validation - All user-controllable input must be validated and filtered for illegal characters as well as content that can be interpreted in the context of an XML data or a query.
Use of custom error pages - Attackers can glean information about the nature of queries from descriptive error messages. Input validation must be coupled with customized error pages that inform about an error without disclosing information about the database or application.

Consider an application that uses an XML database to authenticate its users. The application retrieves the user name and password from a request and forms an XPath expression to query the database. An attacker can successfully bypass authentication and login without valid credentials through XPath Injection. This can be achieved by injecting the query to the XML database with XPath syntax that causes the authentication check to fail. Improper validation of user-controllable input and use of a non-parameterized XPath expression enable the attacker to inject an XPath expression that causes authentication bypass.

23
XML Injection

CAPEC Content Team
The MITRE Corporation
2014-06-23

CAPEC Content Team
The MITRE Corporation
2017-08-04
Updated Resources_Required

CAPEC Content Team
The MITRE Corporation
2018-07-31
Updated References, Related_Weaknesses

CAPEC Content Team
The MITRE Corporation
2020-12-17
Updated Mitigations, Taxonomy_Mappings

CAPEC Content Team
The MITRE Corporation
2021-06-24
Updated Related_Weaknesses

CAPEC Content Team
The MITRE Corporation
2022-02-22
Updated Execution_Flow