CVE-2026-21361
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) vvulnerability 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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Commerce allows high-privileged attackers to inject malicious JavaScript into vulnerable form fields. When victims browse to pages containing the affected fields, the malicious script executes in their browsers, potentially enabling session takeover 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< 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
- 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 installed Adobe Commerce or Magento versionRun the command `php bin/magento --version` from the Magento root directory, or check the `composer.json` file for the `magento/product-community-edition` or `magento/enterprise-edition` version entryAffected if The installed version matches any of 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; 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 high-privileged user accounts existReview the admin user roles and permissions in the Magento admin panel under System > Permissions > User Roles, or query the `admin_user` database table to identify users with elevated privileges such as Administrator or Super User rolesAffected if High-privileged admin accounts with ability to create or edit form content are present in the system
-
Locate vulnerable form fieldsInspect the application code for form field implementations that lack proper output encoding, specifically in admin-facing forms or customer-facing forms that accept user-supplied input and store it in the database without sanitizationAffected if Form fields in the application do not implement output encoding or input validation on submitted values before storing or displaying them
You are affected if your installed Adobe Commerce, Magento, or B2B version matches any of the listed affected versions AND high-privileged users can inject script content into form fields that are rendered without proper encoding.
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. Additionally, implement proper output encoding and input validation/sanitization on the affected form fields to prevent script injection.
Upgrade to Adobe Commerce/Magento 2.4.7-p9 or later (or the latest 2.4.x/2.4.8-p4+ release)
- 1. Back up the Adobe Commerce/Magento database and file system
- 2. Run composer require magento/product-community-edition:<fixed_version> --no-update to specify the target version (e.g., 2.4.7-p9 or later)
- 3. Run composer update to download and install the updated packages
- 4. Run bin/magento setup:upgrade to apply database migrations
- 5. Run bin/magento cache:flush to clear all caches
- 6. Verify the upgrade by logging into the admin panel and checking System > Tools > Cache Management
- 7. Test critical user flows (checkout, admin form submissions) to confirm functionality
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-21361 — 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-21361 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