dbcve.org
CommerceApplication · Adobe

CVE-2026-21309

HIGH · 7.5 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 1.3.3 / 2.4.4 or later.
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.9-alpha3, 2.4.8-p3, 2.4.7-p8, 2.4.6-p13, 2.4.5-p15, 2.4.4-p16 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 security measures and gain unauthorized view access of 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

Adobe Commerce contains an Incorrect Authorization vulnerability allowing attackers to bypass security measures and gain unauthorized view access to sensitive data. The vulnerability has a CVSS 7.5 (High) rating and can be exploited without any user interaction.

MitigationApply the available security patches for Adobe Commerce (2.4.4-p16, 2.4.5-p15, 2.4.6-p13, 2.4.7-p8, 2.4.8-p3, or 2.4.9-alpha3 and later) to address the authorization bypass. Verify all authorization controls are functioning correctly after patching.

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= 2.4.7= 2.4.8= 2.4.9
Commerce B2bApplication
Affected:< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.2= 1.5.3
MagentoCMS
Affected:< 2.4.5= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9

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 Adobe Commerce or Magento version
    Log into the admin panel and navigate to System > Settings > Advanced > Admin > Admin User Model or check the version.php file in the app directory. Alternatively, run: php bin/magento --version
    Affected if The installed version matches < 2.4.4, = 2.4.4, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8, or = 2.4.9 for Adobe Commerce; or < 2.4.5, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8, or = 2.4.9 for Adobe Magento
  2. Check if Adobe Commerce B2B module is installed
    Run command: php bin/magento module:status Magento_B2b or check composer.json for the magento/module-b2b package
    Affected if The B2B module is installed and its version matches < 1.3.3, = 1.3.3, = 1.3.4, = 1.3.5, = 1.4.2, = 1.5.2, or = 1.5.3
  3. Verify the patch level of the installed version
    Check the composer.lock file or run: php bin/magento --version to confirm the exact patch version applied
    Affected if The patch version is below the fixed versions (2.4.4-p16, 2.4.5-p15, 2.4.6-p13, 2.4.7-p8, 2.4.8-p3, or 2.4.9-alpha3 and later)

Your environment is affected if you are running Adobe Commerce or Magento Open Source versions 2.4.4 through 2.4.9 (or < 2.4.5 for Magento) without the corresponding security patches applied, or running Adobe Commerce B2B versions 1.3.3 through 1.5.3 without patches.

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 1.3.3 / 2.4.4 / 2.4.5 or later
Fixed in 1.3.32.4.42.4.5
Interim mitigation

Apply the available security patches for Adobe Commerce (2.4.4-p16, 2.4.5-p15, 2.4.6-p13, 2.4.7-p8, 2.4.8-p3, or 2.4.9-alpha3 and later) to address the authorization bypass. Verify all authorization controls are functioning correctly after patching.

Recommended fix High confidence

Upgrade to the latest patched version for your release line (2.4.4-p16, 2.4.5-p15, 2.4.6-p13, 2.4.7-p8, or 2.4.8-p3), or move to the latest stable release (2.4.7)

  1. 1. Identify your current Adobe Commerce/Magento version by checking the admin panel or running `php bin/magento --version`
  2. 2. Determine which patch version applies to your current release (2.4.4-p16 for 2.4.4.x, 2.4.5-p15 for 2.4.5.x, 2.4.6-p13 for 2.4.6.x, 2.4.7-p8 for 2.4.7.x, or 2.4.8-p3 for 2.4.8.x)
  3. 3. Back up your database and codebase before proceeding with any upgrade
  4. 4. Update Composer dependencies to the appropriate patched version using `composer require magento/product-community-edition=2.4.x-pYY --no-update` (replace x and YY with your target version)
  5. 5. Run `composer update` to fetch the new packages
  6. 6. Clear the cache and regenerate the dependency injection configuration with `bin/magento setup:upgrade`
  7. 7. Deploy static content if running in production mode with `bin/magento setup:static-content:deploy`
  8. 8. Verify the upgrade was successful and test critical user flows
Caveat Adobe patch releases are generally backward-compatible security fixes with minimal breaking changes; always test in a staging environment before deploying to production

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

Fix this in Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing10.0 h
  • Review / QA5.0 h
24.0 hours of engineering $4,080
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,528.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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