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 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.
Security readout for executives and security teams
Plain-English summary
A highly privileged user could save malicious JavaScript in a vulnerable commerce form. When another user views the affected page, the script may run in their browser and enable session takeover. This could expose sensitive information or allow unauthorized changes, but exploitation requires both privileged access and victim interaction.
Executive priority
Prioritize remediation as high, especially for revenue-critical or sensitive commerce environments. The prerequisite of high privileges reduces immediate opportunistic risk, but session takeover could produce serious data exposure and unauthorized changes. Accelerate response where privileged accounts are shared, weakly protected, or suspected compromised.
Technical view
CVE-2026-21284 is stored XSS (CWE-79) affecting specified Adobe Commerce, Commerce B2B, and Magento Open Source releases. CVSS 3.1 is 8.1: network-accessible, low complexity, high privileges required, user interaction required, and changed scope. Successful exploitation can cause high confidentiality and integrity impact without direct availability impact.
Likely exposure
Exposure exists where listed vulnerable releases remain deployed and a potentially malicious or compromised high-privilege account can modify affected form fields. A victim must then visit the page containing the stored content. Exact version boundaries should be confirmed against Adobe APSB26-05 because the supplied structured version data is not fully self-explanatory.
Exploitation context
The supplied sources do not establish active exploitation, and the bundle marks this CVE as absent from KEV. Exploitation requires high privileges and a victim viewing the affected page, limiting opportunistic attacks. However, compromised administrator accounts or malicious insiders could potentially use the flaw for session takeover.
Researcher notes
The vulnerability is stored XSS with changed security scope. Assessment should focus on exact product edition, branch, patch level, privileged write paths, and pages rendering stored field content. The bundle identifies vulnerable Adobe Commerce releases in the description, while its structured affected-version entries require confirmation against the vendor advisory before making branch-specific determinations.
Mitigation direction
Inventory Adobe Commerce, Commerce B2B, and Magento Open Source deployments, including exact release and patch level.
Upgrade vulnerable deployments to the corrected release Adobe specifies for each maintained branch.
Restrict high-privilege accounts and review their recent activity until remediation is complete.
Consult APSB26-05 for exact branch-specific remediation and any newly issued guidance.
Validation and detection
Compare every deployed version and patch level with APSB26-05's affected and corrected version tables.
Confirm upgraded systems report the intended corrected build across all production nodes.
Review privileged-user changes to form fields for unexpected script content or unauthorized modifications.
Investigate browser, application, and session telemetry for anomalous administrative sessions or suspected takeover.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.