dbcve.org
CommerceApplication · Adobe

CVE-2023-29290

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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 bypass a minor functionality. 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 attackers to bypass security features related to minor functionality without user interaction. The flaw affects versions 2.4.6 and earlier, 2.4.5-p2 and earlier, and 2.4.4-p3 and earlier.

MitigationApply the vendor-supplied security patch or update to a patched Adobe Commerce version to remediate the authorization bypass vulnerability.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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
    Run the command bin/magento --version from the Magento root directory, or check the composer.json file for the magento/product-community-edition or magento/product-enterprise-edition version entry.
    Affected if The version is 2.4.6, 2.4.5 (including p1 and p2), 2.4.4 (including p1-p3), 2.4.3, 2.4.2, 2.4.1, 2.4.0, or 2.3.7.
  2. Confirm the exact Adobe Commerce edition and patch level
    Run bin/magento list and review the output for edition type, or inspect the config.php file in the app/etc directory to confirm whether it is Commerce (Enterprise) or Open Source (Community) and note any applied patch versions.
    Affected if The installation is Adobe Commerce or Magento Open Source at any of the affected versions listed, particularly unpatched 2.4.4-p3 and earlier, 2.4.5-p2 and earlier, or 2.4.6 and earlier.
  3. Review admin user role permissions for the vulnerable minor functionality
    Log into the admin panel and navigate to System > Permissions > User Roles, then examine the role resources assigned to each role, particularly any roles with limited or custom permission sets that may be affected by the authorization bypass.
    Affected if The admin configuration allows limited-role users to access functionality that should be restricted, indicating the bypass may be present.
  4. Check for exposure of admin or frontend endpoints to untrusted networks
    Review the server network configuration and web server access logs for requests originating from outside the trusted network that target admin paths or API endpoints, or examine the nginx.conf or .htaccess restrictions.
    Affected if The admin interface or vulnerable endpoints are accessible from the internet or untrusted networks without proper IP restriction.
  5. Inspect security configuration settings related to authorization
    Navigate to Stores > Configuration > Advanced > Admin > Security in the admin panel, or review the env.php file for any custom security settings that control the authorization mechanism for the affected minor functionality.
    Affected if Security settings related to authorization checks are disabled, modified from defaults, or the configuration does not enforce proper authorization for the vulnerable feature.

A user is affected if their Adobe Commerce or Magento installation version falls within 2.4.6 and earlier, 2.4.5-p2 and earlier, or 2.4.4-p3 and earlier (including 2.3.7), and the vulnerable minor functionality is accessible without proper authorization checks.

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-supplied security patch or update to a patched Adobe Commerce version to remediate the authorization bypass vulnerability.

Recommended fix Moderate confidence

Adobe Commerce 2.4.7 or later (which contains the security fix for CVE-2023-29290)

  1. 1. Verify your current Adobe Commerce/Magento installation version by running: bin/magento --version
  2. 2. Back up your entire Adobe Commerce/Magento installation including database and files
  3. 3. Consult the official Adobe security bulletin at helpx.adobe.com for the specific patch or hotfix required for CVE-2023-29290
  4. 4. Apply the appropriate patch (e.g., ACSD-xxxxx for this vulnerability) or upgrade to a fixed release
  5. 5. After applying patch or upgrade, clear the cache: bin/magento cache:flush
  6. 6. Verify the fix by checking the installed version and confirming the security patch is applied
  7. 7. Test critical user workflows to ensure the security feature bypass is remediated
Caveat Review Adobe Commerce 2.4.7 release notes for any compatibility or configuration changes before upgrading; ensure third-party extensions are compatible

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-29290 — 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-29290 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