dbcve.org
CommerceApplication · Adobe

CVE-2023-22248

HIGH · 7.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 →
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.6 (and earlier), 2.4.5-p2 (and earlier) and 2.4.4-p3 (and earlier) are affected by an Incorrect Authorization vulnerability that could result in a security feature bypass. An attacker could leverage this vulnerability to leak another 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 · high confidence

This is an Incorrect Authorization vulnerability in Adobe Commerce (Magento) that allows an attacker to bypass security controls and access another user's data through unauthorized requests. The vulnerability likely involves improper validation of user permissions when accessing specific resources, enabling data leakage without user interaction.

MitigationApply the vendor patch or upgrade Adobe Commerce to the latest version beyond 2.4.6, 2.4.5-p2, and 2.4.4-p3. Review access control policies and implement proper authorization checks for all sensitive data endpoints.

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
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. Identify the installed Adobe Commerce or Magento version
    Check the version file at app/etc/app.json or app/etc/env.php, or run: bin/magento --version. Also check composer.json for the version declaration.
    Affected if The version matches 2.3.7, 2.4.0 through 2.4.6 for Adobe Commerce, or 2.4.4 through 2.4.6 for Adobe Magento.
  2. Confirm the application handles customer or user data
    Verify that the installation has customer accounts enabled. Check if the customer module is active by inspecting app/etc/config.php for Magento_Customer module entry.
    Affected if The customer module is installed and active, as the vulnerability allows access to another user's data.
  3. Check if the web interface or API is publicly accessible
    Review web server configuration and firewall rules. Confirm whether the storefront or API endpoints are exposed to untrusted networks.
    Affected if The application is accessible from untrusted networks, allowing the unauthorized request to be made.
  4. Review custom API endpoints or modules that access user data
    Audit any custom modules in app/code or vendor directories that handle user data access. Look for endpoints that accept user IDs or resource identifiers without proper session validation.
    Affected if Custom modules exist that pass user identifiers in requests without validating the current user session.

If your installed version falls within 2.3.7 to 2.4.6 for Adobe Commerce or 2.4.4 to 2.4.6 for Adobe Magento, and the application handles customer data, you are likely affected by this authorization bypass vulnerability.

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 vendor patch or upgrade Adobe Commerce to the latest version beyond 2.4.6, 2.4.5-p2, and 2.4.4-p3. Review access control policies and implement proper authorization checks for all sensitive data endpoints.

Recommended fix High confidence

Adobe Commerce 2.4.6-p1 or later / Magento Open Source 2.4.6-p1 or later

  1. 1. Identify your current Adobe Commerce or Magento Open Source version using the admin panel or command line (bin/magento --version)
  2. 2. For Adobe Commerce (on-premises) users: Upgrade to version 2.4.6-p1 or later
  3. 3. For Magento Open Source users: Upgrade to version 2.4.6-p1 or later
  4. 4. For users on 2.4.5.x: Upgrade to 2.4.5-p3 or later
  5. 5. For users on 2.4.4.x: Upgrade to 2.4.4-p3 or later
  6. 6. For users on older versions (2.3.7 through 2.4.2): Upgrade to a supported version (2.4.4-p3 or later)
  7. 7. After upgrade, verify the installation by logging into admin and checking the version number
  8. 8. Test critical user flows to ensure authorization controls work correctly
Caveat Review Adobe Commerce upgrade documentation for breaking changes between major versions; test in 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
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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