CWE-643: Improper Neutralization of Data within XPath Expressions ('XPath Injection')
BaseLikelihood of exploit: High
The product uses external input to dynamically construct an XPath expression used to retrieve data from an XML database, but it does not neutralize or incorrectly neutralizes that input. This allows an attacker to control the structure of the query.
The net effect is that the attacker will have control over the information selected from the XML database and may use that ability to control application flow, modify logic, retrieve unauthorized data, or bypass important checks (e.g. authentication).
Consequences
- Access Control: Bypass Protection Mechanism
- Confidentiality: Read Application Data
How to prevent it
- Implementation: Use parameterized XPath queries (e.g. using XQuery). This will help ensure separation between data plane and control plane.
- Implementation: Properly validate user input. Reject data where appropriate, filter where appropriate and escape where appropriate. Make sure input that will be used in XPath queries is safe in that context.
Recent advisories
- GHSA-r7vr-wg3f-8hr9 — Concrete5 CMS contains an XPath injection vulnerability
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor