dbcve.org
CommerceApplication · Adobe

CVE-2026-21310

MEDIUM · 5.3 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 →
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.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 Improper Input Validation vulnerability that could result in a security feature bypass, with limited impact to integrity. 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 versions prior to 2.4.4-p16, 2.4.5-p15, 2.4.6-p13, 2.4.7-p8, 2.4.8-p3, and 2.4.9-alpha3 contain an improper input validation vulnerability that allows attackers to bypass security features through crafted input, with limited impact to data integrity. No user interaction is required for exploitation.

MitigationApply the appropriate Adobe Commerce security patch or upgrade to a fixed version as specified in Adobe's security bulletin. Review input validation points in the application to identify and harden the vulnerable code path.

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
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. Determine installed Adobe Commerce version
    Run the command: php bin/magento --version or check the composer.json file in the Magento root directory for the version field
    Affected if The version displayed is any of: < 2.4.4, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9 (unless it is a patched version: 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+)
  2. Determine installed Adobe Magento version
    Run the command: php bin/magento --version or check composer.json for the magento/version package
    Affected if The version displayed is any of: < 2.4.5, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9 (unless it is a patched version as noted above)
  3. Check if Adobe Commerce B2B module is installed
    Run: php bin/magento module:status | grep -i b2b or check app/etc/config.php for Magento_Company and Magento_B2b entries
    Affected if The B2B module is present and the version is any of: < 1.3.3, 1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.2, or 1.5.3 (unless it is a patched version)
  4. Confirm patch level for affected major versions
    If running 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9, check the composer.lock or run: php bin/magento --version to see the full version string including patch level
    Affected if The full version string shows a patch level lower than p16 for 2.4.4, p15 for 2.4.5, p13 for 2.4.6, p8 for 2.4.7, p3 for 2.4.8, or any version before alpha3 for 2.4.9

You are affected if your Adobe Commerce or Magento installation version matches any of the listed affected versions and is not updated to the specified minimum patched version for your major release line.

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 appropriate Adobe Commerce security patch or upgrade to a fixed version as specified in Adobe's security bulletin. Review input validation points in the application to identify and harden the vulnerable code path.

Recommended fix High confidence

Upgrade to the latest available patch for your release line (e.g., 2.4.4-p16, 2.4.5-p15, 2.4.6-p13, or 2.4.7-p8 or later)

  1. 1. Identify your current Adobe Commerce/Magento installation version using bin/magento --version or composer show magento/product-community-edition
  2. 2. Review the Adobe Security Bulletin (helpx.adobe.com) for the specific patch corresponding to your version
  3. 3. For Adobe Commerce 2.4.4: Apply patch SUPEE-xxxxx or upgrade to 2.4.4-p16
  4. 4. For Adobe Commerce 2.4.5: Apply patch SUPEE-xxxxx or upgrade to 2.4.5-p15
  5. 5. For Adobe Commerce 2.4.6: Apply patch SUPEE-xxxxx or upgrade to 2.4.6-p13
  6. 6. For Magento 2.4.7: Upgrade to 2.4.7-p8 or later
  7. 7. For Adobe Commerce B2b: Apply corresponding B2B patch or upgrade to 1.3.5-pX
  8. 8. Test the upgrade/patch in a staging environment before production deployment
Caveat Patch deployments typically have low risk but always test in staging; ensure compatibility with third-party extensions before upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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