dbcve.org
CommerceApplication · Adobe

CVE-2026-21293

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 access unauthorized resources. 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 a Server-Side Request Forgery (SSRF) vulnerability allowing a high-privileged attacker to manipulate server-side requests and access unauthorized resources, resulting in a security feature bypass. The vulnerability can be exploited without user interaction.

MitigationApply the vendor-provided security patches for the affected Adobe Commerce 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). Additionally, restrict outgoing network connections from the application server and validate/sanitize any user-supplied URLs or request parameters used in server-side requests.

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. Determine Adobe Commerce version
    Run 'php bin/magento --version' from the Magento root directory, or check the composer.json file for the 'version' field under 'require' for 'magento/product-community-edition' or 'magento/product-enterprise-edition'
    Affected if The installed version is 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9, or is earlier than 2.4.4 (any version before 2.4.4)
  2. Determine Adobe Magento version
    Run 'php bin/magento --version' or check the composer.json file for the version of 'magento/magento2-base' package
    Affected if The installed version is 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9, or is earlier than 2.4.5 (any version before 2.4.5)
  3. Determine Adobe Commerce B2B version
    Run 'php bin/magento --version' or check composer.json for 'magento/module-b2b' package 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 is earlier than 1.3.3, and the main Commerce version is within the affected range
  4. Verify outgoing network access
    Review server firewall rules and application network configuration to determine if the web server process can make outbound HTTP/HTTPS connections to arbitrary hosts
    Affected if Outbound network connections are allowed from the application server, which is required for the SSRF vulnerability to be exploitable

Your environment is affected if you are running any Adobe Commerce, Adobe Commerce B2B, or Adobe Magento version within the listed affected ranges, and your server has the ability to make outgoing network requests.

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-provided security patches for the affected Adobe Commerce 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). Additionally, restrict outgoing network connections from the application server and validate/sanitize any user-supplied URLs or request parameters used in server-side requests.

Recommended fix Moderate confidence

Adobe Commerce/Magento 2.4.7-p1 or later (or latest 2.4.x stable release); Commerce B2B 1.3.6-p1 or later

  1. 1. Identify your current Adobe Commerce/Magento version using the admin panel (System > Tools > Web Setup Wizard) or CLI command: bin/magento --version
  2. 2. For Adobe Commerce (on-premise) users: Upgrade to version 2.4.7-p1 or later (or the latest 2.4.x release)
  3. 3. For Magento Open Source users: Upgrade to version 2.4.7-p1 or later
  4. 4. For Adobe Commerce B2B users: Ensure Commerce is updated first, then upgrade B2B extension to version 1.3.6-p1 or later
  5. 5. Run composer update in your project root: composer require magento/product-community-edition=2.4.7-p1 --no-update (adjust version as needed)
  6. 6. After composer update completes, clear the cache: bin/magento cache:clean
  7. 7. Run the upgrade command to update the database schema: bin/magento setup:upgrade
  8. 8. Re-compile the DI configuration if in production mode: bin/magento setup:di:compile
Caveat Standard Magento upgrade risks apply - review release notes for breaking changes, test in staging environment before production deployment, 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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