dbcve.org
CommerceApplication · Adobe

CVE-2026-21294

MEDIUM · 5.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 →
61/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.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 a Server-Side Request Forgery (SSRF) vulnerability that could result in a Security feature bypass. A high-privileged attacker could exploit this vulnerability to manipulate server-side requests and bypass security controls. 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 a Server-Side Request Forgery (SSRF) vulnerability allowing high-privileged attackers to manipulate server-side requests and bypass security controls. The vulnerability affects versions 2.4.4-p16 through 2.4.9-alpha3 and exploitation requires no user interaction.

MitigationApply the vendor-supplied patches for the respective versions (2.4.4-p16, 2.4.5-p15, 2.4.6-p13, 2.4.7-p8, 2.4.8-p3, 2.4.9-alpha3) and limit administrative access to trusted high-privileged users only.

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
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/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. Check Adobe Commerce version via command line
    Run `bin/magento --version` or `composer show magento/product-community-edition 2>/dev/null | grep version` in the Magento root directory
    Affected if The version displayed is 2.4.4 (any patch before p16), 2.4.5 (any patch before p15), 2.4.6 (any patch before p13), 2.4.7 (any patch before p8), 2.4.8 (any patch before p3), or 2.4.9-alpha3, or any version lower than 2.4.4
  2. Check Adobe Commerce version via composer
    Examine the `composer.json` file in the Magento root directory and look for the version specified under `require` -> `magento/product-community-edition` or `magento/product-enterprise-edition`
    Affected if The version listed is less than 2.4.4-p16, or falls within 2.4.4 to 2.4.9-alpha3 without the corresponding security patch (p16, p15, p13, p8, p3, or alpha3)
  3. Check Adobe Commerce B2B version
    Run `composer show magento/module-b2b 2>/dev/null | grep version` or check composer.json for `magento/module-b2b` version
    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 any version below 1.3.3
  4. Check Adobe Magento version via admin panel
    Log into the admin panel and scroll to the footer of any page to view the version number displayed
    Affected if The version shown in the admin footer matches any of the vulnerable versions listed above (2.4.4 through 2.4.9-alpha3 without patches)
  5. Verify administrative access controls
    Review admin user accounts and roles in the admin panel under System -> Permissions -> Users and Roles to determine if any untrusted or unexpected users have high-privileged access
    Affected if There are high-privileged admin users who are untrusted or unauthorized, as the vulnerability requires a high-privileged attacker to exploit

You are affected if your Adobe Commerce or Magento installation is version 2.4.4 through 2.4.9-alpha3 without the vendor-supplied security patches applied, and you have untrusted high-privileged users with administrative access.

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-supplied patches for the respective versions (2.4.4-p16, 2.4.5-p15, 2.4.6-p13, 2.4.7-p8, 2.4.8-p3, 2.4.9-alpha3) and limit administrative access to trusted high-privileged users only.

Recommended fix Moderate confidence

Adobe Commerce 2.4.7-p9+ or latest 2.4.x release | Magento Open Source 2.4.7-p9+ or latest 2.4.x release

  1. 1. Identify your current Adobe Commerce/Magento installation version using the command line: bin/magento --version or check composer.json
  2. 2. For Adobe Commerce (including B2B): Review available security patches at helpx.adobe.com/security.html and upgrade to the latest available patch for your major version line
  3. 3. For Magento Open Source: Upgrade to the latest patch release within your current minor version (e.g., if on 2.4.6, upgrade to 2.4.6-p14 or later)
  4. 4. Run composer require magento/product-community-edition=<version> --no-update to specify the new version, replacing <version> with the target patch release
  5. 5. Run composer update to apply the changes
  6. 6. After update completes, run bin/magento setup:upgrade to apply database migrations
  7. 7. Clear caches: bin/magento cache:flush
  8. 8. Re-index: bin/magento indexer:reindex
Caveat Patch upgrades typically contain only security fixes and should not introduce breaking changes; however, always review release notes before upgrading and test in a staging environment

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

Fix this in Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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