dbcve.org
CommerceApplication · Adobe

CVE-2023-38220

HIGH · 7.5 CVSS v3.1 Published 2023-10-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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.7-beta1 (and earlier), 2.4.6-p2 (and earlier), 2.4.5-p4 (and earlier) and 2.4.4-p5 (and earlier) are affected by an Improper Authorization vulnerability that could lead in a security feature bypass in a way that an attacker could access unauthorised data. 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

This is an Improper Authorization vulnerability in Adobe Commerce (Magento) that allows authenticated or anonymous attackers to bypass security controls and access data they are not authorized to view. The vulnerability requires no user interaction for exploitation.

MitigationApply the appropriate security patch released by Adobe for the specific Adobe Commerce version in use, or upgrade to a patched version that addresses CVE-2023-38220.

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= 2.4.7
MagentoCMS
Affected:= 2.4.4= 2.4.5= 2.4.6= 2.4.7

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Check Adobe Commerce/Magento installed version via CLI
    Run `bin/magento --version` or `php bin/magento --version` from the Magento root directory
    Affected if The version output matches any of: 2.3.7, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7
  2. Check version via composer
    Run `composer show magento/product-commerce 2>/dev/null | grep version` or inspect the composer.lock file for the installed magento package version
    Affected if The installed magento/product-commerce version matches any of: 2.3.7, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7
  3. Check version via admin panel
    Log into the admin panel and navigate to System > Configuration > Advanced > Advanced > Module Output or check the footer of any admin page for the version string
    Affected if The displayed version matches any of the affected versions listed above
  4. Check Magento Open Source version if applicable
    If using Magento Open Source rather than Adobe Commerce, run `composer show magento/product-community-edition 2>/dev/null | grep version` or check composer.lock
    Affected if The installed magento/product-community-edition version matches any of: 2.4.4, 2.4.5, 2.4.6, 2.4.7

The environment is affected if the installed Adobe Commerce or Magento version matches 2.3.7, 2.4.0 through 2.4.7 (Commerce) or 2.4.4 through 2.4.7 (Magento).

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

Apply the appropriate security patch released by Adobe for the specific Adobe Commerce version in use, or upgrade to a patched version that addresses CVE-2023-38220.

Recommended fix Moderate confidence

Adobe Commerce 2.4.4-p6+, 2.4.5-p5+, 2.4.6-p3+, or 2.4.7-p1+ (depending on your current version)

  1. 1. Review the Adobe Security Bulletin (APSB23-40) for CVE-2023-38220 on helpx.adobe.com to obtain the specific patch or updated version.
  2. 2. For Adobe Commerce 2.4.4: Upgrade to 2.4.4-p6 or later which contains the security fix.
  3. 3. For Adobe Commerce 2.4.5: Upgrade to 2.4.5-p5 or later which contains the security fix.
  4. 4. For Adobe Commerce 2.4.6: Upgrade to 2.4.6-p3 or later which contains the security fix.
  5. 5. For Adobe Commerce 2.4.7: Upgrade to the latest 2.4.7 release (2.4.7-p1 or later) which contains the security fix.
  6. 6. Before upgrading in production, test the patch/upgrade in a staging environment to verify compatibility with custom extensions and themes.
  7. 7. After upgrading, verify that the improper authorization vulnerability is resolved by testing unauthorized access attempts.
Caveat Minor patch upgrades typically have low risk but always test in staging first as custom extensions may require compatibility updates

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

Fix this in Commerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-38220 — 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-38220 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