CVE-2026-21284
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 · moderate confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in Adobe Commerce affecting multiple form fields in the admin interface. A high-privileged attacker can inject malicious JavaScript payloads into vulnerable form fields, which persist and execute when other users navigate to pages containing those fields, enabling session hijacking and privilege escalation.
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< 1.3.3= 1.3.3= 1.3.4= 1.3.5= 1.4.2= 1.5.2= 1.5.3< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9< 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
- Low
- Privileges
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify the installed Adobe Commerce or Magento versionRun the command bin/magento --version from the web root directory, or check the composer.json file for the version attributeAffected if The version matches or falls within the affected ranges: Adobe Commerce < 2.4.4, = 2.4.4, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8, = 2.4.9; or Adobe Magento < 2.4.5, = 2.4.5, = 2.4.6, = 2.4.7, = 2.4.8, = 2.4.9; or Adobe Commerce B2b < 1.3.3, = 1.3.3, = 1.3.4, = 1.3.5, = 1.4.2, = 1.5.2, = 1.5.3
-
Determine if Adobe Commerce B2B extension is installedRun bin/magento module:status or check the config.php file for the Magento_SharedCatalog or Magento_B2b modulesAffected if The B2B extension is enabled and its version matches any of the affected B2B version ranges listed above
-
Audit admin-accessible form fields for potential injection pointsReview the codebase for form controllers or UI components that accept user input and render it back without proper sanitization, particularly in admin panel areasAffected if Custom or extended form fields exist that do not use Magento's built-in XSS protection methods when rendering user-supplied data
-
Search database for stored malicious scriptsQuery core tables where form data is stored, looking for patterns like script tags, javascript:, or encoded HTML entities that may represent XSS payloadsAffected if Any records contain suspicious JavaScript code or HTML tags embedded in text fields that were not intentionally stored by legitimate users
You are affected if your Adobe Commerce or Magento installation version falls within the listed affected ranges AND your environment has high-privileged users with access to the vulnerable 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
Apply output encoding/sanitization to all user-controllable form fields in the admin panel; update to patched versions when released by Adobe.
Adobe Commerce/Magento 2.4.7-p9 (or later in your release train)
- 1. Identify your current Adobe Commerce/Magento version by running: bin/magento --version
- 2. Back up your database and filesystem before proceeding with any upgrade
- 3. For Adobe Commerce (Magento Commerce) users: Upgrade to version 2.4.7-p9 or later, or 2.4.6-p14 or later, or 2.4.5-p16 or later, or 2.4.4-p17 or later
- 4. For Magento Open Source users: Upgrade to the corresponding patched version matching your release line
- 5. Alternatively, apply the relevant Adobe security patch (e.g., MDVA-XXXXX or equivalent) if available for your specific version
- 6. Clear the Magento cache after upgrade: bin/magento cache:flush
- 7. Verify the upgrade was successful and test the affected form fields for proper input sanitization
- 8. Re-index all data if necessary: bin/magento indexer:reindex
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2026-21284 — 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-21284 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