dbcve.org
CommerceApplication · Adobe

CVE-2023-38209

MEDIUM · 6.5 CVSS v3.1 Published 2023-08-09
Fix available
A fix is available. Upgrade to 2.4.4 or later.
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-p1 (and earlier), 2.4.5-p3 (and earlier) and 2.4.4-p4 (and earlier) are affected by an Incorrect Authorization vulnerability that could lead to a Security feature bypass. A low-privileged attacker could leverage this vulnerability to access other user's 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 · moderate confidence

Adobe Commerce contains an Incorrect Authorization vulnerability allowing low-privileged authenticated users to bypass security controls and access data belonging to other users. This is a broken access control issue in the application's authorization logic that enables horizontal privilege escalation.

MitigationUpdate Adobe Commerce to the latest patched version that addresses CVE-2023-38209. Review and audit user authorization checks across the application to ensure consistent enforcement of access controls.

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.4.4= 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 installed Adobe Commerce version
    Run the command 'bin/magento --version' from the Adobe Commerce root directory, or check the 'composer.json' file for the 'version' or 'magento/product-community-edition' version entry
    Affected if The version is 2.4.4, 2.4.5, 2.4.6, or any version lower than 2.4.4
  2. Confirm low-privileged user accounts exist
    Log into the Adobe Commerce admin panel and navigate to 'Customers' > 'All Customers' or 'System' > 'Permissions' > 'User Roles' to verify there are non-admin user accounts with limited privileges
    Affected if There are authenticated users with roles other than 'Administrators' (such as 'Customers' or limited 'Custom' roles)
  3. Verify the application handles user-specific data retrieval
    As a low-privileged authenticated user (non-admin), attempt to access or modify data that belongs to a different user account, such as viewing another customer's order history, address book, or account information through API or direct URL access
    Affected if Low-privileged users can access, view, or modify data belonging to other users (horizontal privilege escalation is possible)

Your environment is affected if the installed Adobe Commerce version is 2.4.4, 2.4.5, 2.4.6, or any version below 2.4.4 AND the application has non-admin user accounts that could potentially access other users' data.

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
Upgrade available Upgrade to 2.4.4 or later
Fixed in 2.4.4
Interim mitigation

Update Adobe Commerce to the latest patched version that addresses CVE-2023-38209. Review and audit user authorization checks across the application to ensure consistent enforcement of access controls.

Recommended fix Moderate confidence

Adobe Commerce 2.4.7 or later, or the latest p5+ patch for 2.4.4, p4+ patch for 2.4.5, or p2+ patch for 2.4.6

  1. 1. Review the Adobe Commerce release notes and security patches for versions 2.4.4-p4, 2.4.5-p3, and 2.4.6-p1 to confirm the specific patch addressing CVE-2023-38209.
  2. 2. Identify your current Adobe Commerce version by running: bin/magento --version
  3. 3. Create a full backup of the database and filesystem before applying any updates.
  4. 4. Upgrade to the latest available Adobe Commerce release that includes the security fix for this vulnerability. Based on Adobe's patch naming convention, this would be version 2.4.4-p5 or later for the 2.4.4 branch, 2.4.5-p4 or later for the 2.4.5 branch, and 2.4.6-p2 or later for the 2.4.6 branch.
  5. 5. Alternatively, upgrade to the most recent stable release (2.4.7 or later) which should include all recent security patches.
  6. 6. After upgrading, clear the cache: bin/magento cache:flush
  7. 7. Verify the installation: bin/magento setup:upgrade
  8. 8. Re-index all data: bin/magento indexer:reindex
Caveat Review Adobe Commerce upgrade documentation for potential breaking changes between minor version jumps; test thoroughly in a staging environment before production deployment

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

Fix this in Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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