dbcve.org
Commerce B2bApplication · Adobe

CVE-2026-21289

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 affects multiple versions (2.4.4-p16 through 2.4.9-alpha3) and can be exploited without any user interaction.

MitigationApply the vendor-released security patches for the specific Adobe Commerce version in use, or upgrade to a patched version. Review access controls and audit authorization configurations as a secondary measure.

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
Commerce B2bApplication
Affected:< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.2= 1.5.3
CommerceApplication
Affected:< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9
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 product type
    Determine whether the installation is Adobe Commerce, Adobe Commerce B2b, or Magento Open Source by checking the composer.json file in the project root for the package name (e.g., magento/product-community-edition, magento/product-enterprise-edition, or magento/project-community-edition)
    Affected if The product is Adobe Commerce or Adobe Magento (Adobe Commerce B2b is a separate module)
  2. Check the installed Adobe Commerce or Magento version
    Run the CLI command: php bin/magento --version OR inspect the composer.lock file for the version of the magento/magento2-base package OR log into the Admin panel and check System > Configuration > General > Advanced > Advanced (the version is displayed at the bottom)
    Affected if The displayed version matches one of the affected ranges
  3. Verify Adobe Commerce B2b module version if installed
    If Adobe Commerce B2b is installed, check the composer.lock for magento/module-b2b or run: php bin/magento module:status Magento_B2b
    Affected if The B2b module version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.2, or 1.5.3, or less than 1.3.3
  4. Compare against Adobe Commerce affected versions
    If using Adobe Commerce (not Magento Open Source), verify the version is 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9, or any version below 2.4.4
    Affected if The version falls within these ranges: < 2.4.4, = 2.4.4, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8, = 2.4.9
  5. Compare against Adobe Magento affected versions
    If using Magento Open Source, verify the version is 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9, or any version below 2.4.5
    Affected if The version falls within these ranges: < 2.4.5, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8, = 2.4.9

You are affected if your Adobe Commerce or Magento installation version matches any of the specific versions listed in the affected ranges for your product type, since this is an authorization bypass that requires no user interaction to exploit.

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 vendor-released security patches for the specific Adobe Commerce version in use, or upgrade to a patched version. Review access controls and audit authorization configurations as a secondary measure.

Recommended fix Moderate confidence

Adobe Commerce/Magento 2.4.7-p9+, 2.4.8+, or respective patched versions (2.4.4-p17+, 2.4.5-p16+, 2.4.6-p14+); B2B 1.3.6+

  1. 1. Identify your current Adobe Commerce/Magento version using the admin panel (System > Configuration > General) or command line: bin/magento --version
  2. 2. For Magento Open Source, upgrade to 2.4.7-p1 or later, or ideally 2.4.8 or later stable release
  3. 3. For Adobe Commerce (Commerce), upgrade to the appropriate patched version: 2.4.4-p17+, 2.4.5-p16+, 2.4.6-p14+, 2.4.7-p9+, or 2.4.8-p4+
  4. 4. For Adobe Commerce B2B, upgrade to version 1.3.6 or later
  5. 5. Before upgrading in production, test the upgrade in a staging environment to verify compatibility
  6. 6. Create a full backup of the database and files before performing the upgrade
  7. 7. Run the upgrade using Composer: composer require magento/product-community-edition=<version> --no-update, then composer update
  8. 8. After upgrade, clear caches: bin/magento cache:flush
Caveat Major upgrades may introduce breaking changes to custom extensions or themes; thoroughly test in staging environment before production deployment

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

Fix this in Commerce B2b Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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