CVE-2026-21311
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 · uneditedAdobe 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 high-privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field. A successful attacker can abuse this to achieve session takeover, increasing the confidentiality, and integrity impact to high. 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 confidenceAdobe Commerce versions prior to the listed patches contain a stored Cross-Site Scripting (XSS) vulnerability in form fields that allows a high-privileged attacker (likely admin) to inject malicious JavaScript. When victims browse to pages containing the compromised field, the script executes in their browser, enabling session takeover.
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< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.2= 1.5.3< 2.4.5= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine Adobe Commerce versionRun the CLI command: bin/magento --version or check the composer.json file in the installation root for the magento/product-community-edition versionAffected if Installed version is 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9, or any version prior to 2.4.4
-
Determine Adobe Commerce B2B versionRun: composer show magento/module-b2b 2>/dev/null | grep version or check composer.json for magento/module-b2b versionAffected if Installed B2B version is 1.3.3, 1.3.4, 1.3.5, 1.4.2, 1.5.2, or 1.5.3, or any version prior to 1.3.3
-
Determine Adobe Magento versionRun: bin/magento --version or inspect the composer.json for magento/magento2-base version if using Magento Open SourceAffected if Installed version is 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9, or any version prior to 2.4.5
-
Review admin form fields for injected scriptsQuery the database for suspicious script tags in configurable form tables (e.g., core_config_data, admin_user, or custom form tables), or inspect page source of admin forms for unexpected script elementsAffected if Any form field in the database or rendered page contains unsanitized script tags or event handlers (onerror, onload, onclick, etc.)
-
Check admin user accounts for compromiseQuery the admin_user table for any users with unexpected attributes or review recent admin login activity logs for suspicious sessionsAffected if Admin account modifications occurred that were not performed by known administrators, or sessions are originating from unexpected IP addresses
You are affected if your Adobe Commerce, Commerce B2B, or Magento installation version falls within the listed affected version ranges and an admin-level user has injected malicious scripts into form fields.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.3.32.4.42.4.5
Update Adobe Commerce to the latest patched version (2.4.9-alpha3, 2.4.8-p3, 2.4.7-p8, 2.4.6-p13, 2.4.5-p15, or 2.4.4-p16 and later). Implement input sanitization on vulnerable form fields and consider Content Security Policy headers as defense-in-depth.
Adobe Commerce 2.4.7-p8 or later, or Magento Open Source 2.4.7 or later
- Identify the exact Adobe Commerce/Magento version currently installed using bin/magento --version
- For Commerce versions 2.4.4.x: Apply security patch SUPEE-11314 (or equivalent QPT patch for the quarter) which includes the XSS fix
- For Commerce versions 2.4.5.x: Apply security patch SUPEE-11314 or later quarterly patch
- For Commerce versions 2.4.6.x: Apply security patch SUPEE-11314 or later quarterly patch
- For Commerce versions 2.4.7.x: Apply security patch SUPEE-11314 or later quarterly patch
- For Commerce B2b versions 1.3.3.x-1.3.5.x: Apply the corresponding B2B security patch
- After applying the patch, clear the Magento cache: bin/magento cache:clean
- Verify the patch was applied successfully by checking for the patch file in app/etc/patches/ or reviewing Applied Patches.md
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21311 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-21311 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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