Security Resilience

CVE-2023-29289

Adobe Commerce 2.3.7 … 2.4.6

Published
15 June 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0088 58th percentile
Risk Priority 52 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-29289 is a medium-severity aka Blind XPath Injection (CWE-91) vulnerability in Adobe Commerce. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Security Account Manager (T1003.002); ranked in the top 42% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Adobe Commerce versions 2.4.6 (and earlier), 2.4.5-p2 (and earlier) and 2.4.4-p3 (and earlier) are affected by an XML Injection vulnerability. An attacker with low privileges can trigger a specially crafted script to a security feature bypass. Exploitation of this issue…

more

does not require user interaction.

CWE(s)
CWE-91

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
attack.mitre.org →
T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
attack.mitre.org →
T1011.001 Exfiltration Over Bluetooth Exfiltration
Adversaries may attempt to exfiltrate data over Bluetooth rather than the command and control channel.
attack.mitre.org →
T1018 Remote System Discovery Discovery
Adversaries may attempt to get a listing of other systems by IP address, hostname, or other logical identifier on a network that may be used for Lateral Movement from the current system.
attack.mitre.org →
T1021 Remote Services Lateral Movement
Adversaries may use [Valid Accounts](https://attack.
attack.mitre.org →
T1021.001 Remote Desktop Protocol Lateral Movement
Adversaries may use [Valid Accounts](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-22247Same product: Adobe Commerce
CVE-2023-38249Same product: Adobe Commerce
CVE-2024-39406Same product: Adobe Commerce
CVE-2024-39399Same product: Adobe Commerce
CVE-2023-38221Same product: Adobe Commerce
CVE-2023-38250Same product: Adobe Commerce
CVE-2024-20759Same product: Adobe Commerce
CVE-2024-39400Same product: Adobe Commerce
CVE-2023-38219Same product: Adobe Commerce
CVE-2024-39403Same product: Adobe Commerce

Affected Assets

adobe
commerce
2.3.7, 2.4.0, 2.4.1, 2.4.2, 2.4.3
adobe
magento
2.4.4, 2.4.5, 2.4.6

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
blocks

Secure SDLC directly requires input neutralization and validation that eliminates XML injection flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.15 Logging partial match
finds

Logging can record injection attempts for detection but does not prevent the weakness.

A.8.16 Monitoring activities partial match
finds

Monitoring can detect exploitation but provides no preventive control over XML handling.

A.8.19 Installation of software on operational systems partial match
removes
A.8.25 Secure development life cycle partial match
blocks

A.8.25 mandates secure SDLC practices (secure coding guidelines, security requirements, checkpoints, testing including code scans) that reach XML injection when developers follow them, but leaves a minority slice where implementation is incomplete or the outsourced supplier assurance fails.

A.8.26 Application security requirements partial match
blocks

A.8.26 requires identifying and specifying security requirements (including resilience against SQL injections and input validation) determined via risk assessment; this can address XML injection for some applications but leaves a bounded remainder where requirements are scoped narrowly, not fully enforced in code, or miss XML-specific neutralization.

A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates security-by-design principles, secure architecture patterns (defense-in-depth, least privilege, distrust external input, fail securely), design reviews against known attack patterns, and data validation/sanitization guidance that reach a slice of XML injection cases, but leaves the dominant code-level neutralization defect untouched without further implementation-specific controls.

References