Cyber Resilience

CVE-2023-29289

Adobe Commerce 2.3.7 … 2.4.6

Published
15 June 2023
Modified
21 November 2024
Patch / 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 56th percentile
Risk Priority 52 floored blend · peak EPSS

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 Content Injection (T1659); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

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)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
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-2024-39409Same product: Adobe Commerce
CVE-2023-29292Same product: Adobe Commerce
CVE-2023-38249Same product: Adobe Commerce
CVE-2024-39406Same product: Adobe Commerce
CVE-2023-38221Same product: Adobe Commerce
CVE-2024-49521Same product: Adobe Commerce
CVE-2024-39410Same product: Adobe Commerce
CVE-2023-26366Same product: Adobe Commerce
CVE-2023-38250Same 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 mostly match
prevents

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.

finds

Security testing catches XML injection during development but does not itself implement the fix.

A.8.15 Logging partial match
finds

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

finds

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

prevents

Secure SDLC mandates input validation and output encoding that directly prevent XML injection.

prevents

Application security requirements explicitly call for defenses against injection flaws including XML.

prevents

Secure architecture principles reduce attack surface but do not prescribe XML-specific controls.

References