dbcve.org
Commerce B2bApplication · Adobe

CVE-2026-21292

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low-privileged attacker attacker to inject malicious scripts into vulnerable form fields. Exploitation of this issue requires user interaction in that a victim must browse to the page containing the vulnerable field.

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Commerce allows low-privileged attackers to inject malicious JavaScript into form fields. The malicious payload persists in the database and executes when other users (including administrators) view the affected pages, as exploitation requires user interaction where a victim browses to the page containing the compromised field.

MitigationUpdate Adobe Commerce to the latest patched version. Additionally, implement proper input validation and output encoding on all form fields that accept user-supplied content to prevent XSS.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Identify Adobe Commerce or Magento installation version
    Run the command: php bin/magento --version or check the composer.json file in the Adobe Commerce/Magento root directory for the version entry
    Affected if The installed version matches any of these ranges: Adobe Commerce B2b: < 1.3.3, = 1.3.3, = 1.3.4, = 1.3.5, = 1.4.2, = 1.5.2, = 1.5.3; Adobe Commerce: < 2.4.4, = 2.4.4, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8, = 2.4.9; Adobe Magento: < 2.4.5, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8, = 2.4.9
  2. Determine if Adobe Commerce B2B module is installed and enabled
    Run: php bin/magento module:status Magento_Company or check the app/etc/config.php file for Magento_Company module status
    Affected if The B2B module is enabled and the Adobe Commerce B2b version falls within the affected ranges listed above
  3. Inspect database for suspicious script tags in form input tables
    Query user-submitted data tables such as customer_address, quote_address, order_address, or any custom form tables for patterns like <script, javascript:, onerror=, onload=, or other HTML/script injections. Example SQL: SELECT * FROM customer_address_entity_varchar WHERE value LIKE '%<script%' OR value LIKE '%javascript:%';
    Affected if Any records contain encoded or raw script injection payloads in form fields that are rendered without proper output encoding
  4. Review admin access logs for suspicious low-privilege user activity
    Examine application logs in var/log/ or database audit tables for actions taken by low-privilege users that created or modified records in form-related tables, especially in rapid succession or containing unusual character sequences
    Affected if Logs show low-privilege users creating or modifying records that contain JavaScript or HTML tags in input fields

You are affected if your Adobe Commerce or Magento installation version is within the affected ranges listed AND your database contains persisted XSS payloads in form fields that could execute when viewed by other users including administrators.

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

Update Adobe Commerce to the latest patched version. Additionally, implement proper input validation and output encoding on all form fields that accept user-supplied content to prevent XSS.

Recommended fix Moderate confidence

Commerce B2b: 1.3.6+ | Commerce: 2.4.7+ | Magento Open Source: 2.4.8+

  1. 1. Identify your current Adobe Commerce, Commerce B2b, or Magento installation version using the command line or admin panel.
  2. 2. For Commerce B2b (versions 1.3.3, 1.3.4, 1.3.5 or earlier): Upgrade to Commerce B2b version 1.3.6 or later.
  3. 3. For Adobe Commerce (versions 2.4.4, 2.4.5, 2.4.6 or earlier): Upgrade to Adobe Commerce version 2.4.7 or later.
  4. 4. For Magento Open Source (versions 2.4.5, 2.4.6, 2.4.7 or earlier): Upgrade to Magento Open Source version 2.4.8 or later.
  5. 5. After upgrading, clear the Magento cache using: php bin/magento cache:flush
  6. 6. Verify the upgrade was successful and test that the vulnerable form fields properly encode user input.
  7. 7. Ensure all extensions and custom code are compatible with the new Magento version before deploying to production.
Caveat Major version upgrades may introduce breaking changes to custom themes, extensions, or integrations; thoroughly test in a 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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,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 $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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