dbcve.org
CommerceApplication · Adobe

CVE-2023-29289

MEDIUM · 6.5 CVSS v3.1 Published 2023-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 does not require user interaction.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Adobe Commerce (Magento) versions prior to 2.4.6-p1, 2.4.5-p3, and 2.4.4-p4 contain an XML Injection vulnerability in a security feature. An authenticated attacker with low privileges can inject malicious XML content to bypass security controls. No user interaction is required for exploitation.

MitigationUpgrade Adobe Commerce to version 2.4.6-p1, 2.4.5-p3, 2.4.4-p4 or later. Apply the official Adobe security patch if immediate upgrade is not feasible. Review and sanitize any XML input handling in custom modules.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CommerceApplication
Affected:= 2.3.7= 2.4.0= 2.4.1= 2.4.2= 2.4.3= 2.4.4= 2.4.5= 2.4.6
MagentoCMS
Affected:= 2.4.4= 2.4.5= 2.4.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Adobe Commerce version
    Run the command 'php bin/magento --version' from the Magento root directory, or inspect the composer.json file for the 'version' field under the 'magento/product-enterprise-edition' or 'magento/module-...' packages.
    Affected if The installed version is 2.3.7, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, or 2.4.6 (any version prior to the patched releases).
  2. Confirm product type
    Check if the installation is Adobe Commerce (Magento Open Source differences apply). Inspect composer.json for 'magento/product-enterprise-edition' (Adobe Commerce) or 'magento/product-community-edition' (Magento Open Source).
    Affected if The product is Adobe Commerce version 2.3.7 through 2.4.6, as listed in the affected versions.
  3. Identify XML handling in security features
    Review custom modules and configuration files in app/code or vendor/ for XML parsing or processing related to security controls. Look for usage of SimpleXML, DOMDocument, or XML validation in security-related code paths.
    Affected if The environment processes XML input within security features without proper sanitization, enabling the injection vector.
  4. Verify authenticated access exposure
    Review user role configurations under Stores > Settings > All Users in the admin panel. Determine if low-privilege user accounts (with limited roles) can access areas that handle XML-based security configurations.
    Affected if Low-privilege authenticated users can access or modify XML-based security settings without sufficient input validation.

A user is affected if their Adobe Commerce installation version is 2.3.7 through 2.4.6 (any version prior to 2.4.6-p1, 2.4.5-p3, or 2.4.4-p4) and the system processes XML content in security-related functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Adobe Commerce to version 2.4.6-p1, 2.4.5-p3, 2.4.4-p4 or later. Apply the official Adobe security patch if immediate upgrade is not feasible. Review and sanitize any XML input handling in custom modules.

Recommended fix High confidence

Apply vendor security patch: 2.4.4-p3 or later for 2.4.4.x, 2.4.5-p2 or later for 2.4.5.x, or 2.4.7+ for 2.4.6 and earlier

  1. 1. Identify current Adobe Commerce/Magento version by running `bin/magento --version` or checking the admin panel under System > Configuration > Advanced > Advanced
  2. 2. Review the official Adobe security bulletin at helpx.adobe.com for CVE-2023-29289 to obtain the specific patch file
  3. 3. Back up the entire Magento database and codebase before applying any patches
  4. 4. Apply the security patch using the standard patch command: `patch -p1 < patch_file.patch`
  5. 5. After patch application, clear the Magento cache: `bin/magento cache:flush`
  6. 6. Verify the patch was applied successfully and the version reflects the patched state
  7. 7. Test that XML-related functionality works correctly and the vulnerability is remediated
Caveat Security patches typically have minimal breaking changes but should be tested in a staging environment; verify compatibility with custom modules and themes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Commerce Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29289 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-29289 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data