CVE Vulnerabilities


XML Injection (aka Blind XPath Injection)

Published: Mar 27, 2023 | Modified: Apr 04, 2023
CVSS 3.x
CVSS 2.x

Adobe Commerce versions 2.4.4-p2 (and earlier) and 2.4.5-p1 (and earlier) are affected by an XML Injection vulnerability that could lead to arbitrary file system read. An unauthenticated attacker can force the application to make arbitrary requests via injection of arbitrary URLs. Exploitation of this issue does not require user interaction.


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.

Affected Software

Name Vendor Start Version End Version
Commerce Adobe * 2.4.4 (excluding)
Commerce Adobe 2.4.4 (including) 2.4.4 (including)
Commerce Adobe 2.4.4-p1 (including) 2.4.4-p1 (including)
Commerce Adobe 2.4.4-p2 (including) 2.4.4-p2 (including)
Commerce Adobe 2.4.5 (including) 2.4.5 (including)
Commerce Adobe 2.4.5-p1 (including) 2.4.5-p1 (including)
Magento_open_source Adobe * 2.4.4 (excluding)
Magento_open_source Adobe 2.4.4 (including) 2.4.4 (including)
Magento_open_source Adobe 2.4.4-p1 (including) 2.4.4-p1 (including)
Magento_open_source Adobe 2.4.4-p2 (including) 2.4.4-p2 (including)
Magento_open_source Adobe 2.4.5 (including) 2.4.5 (including)
Magento_open_source Adobe 2.4.5-p1 (including) 2.4.5-p1 (including)

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.