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 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
CVE-2026-21290 is a high-severity stored cross-site scripting flaw in Adobe Commerce. A low-privileged attacker could save malicious script content in a vulnerable field. If another user views the affected page, the script may run in their browser and enable session takeover, exposing sensitive data or allowing unauthorized actions.
Executive priority
Treat this as a high-priority remediation because successful exploitation could compromise privileged sessions and business data. Accelerate action for externally reachable stores or environments with delegated content-management accounts. Emergency shutdown is not supported by the supplied evidence, but prompt patching and exposure review are warranted.
Technical view
The vulnerability is stored XSS (CWE-79) with CVSS 3.1 score 8.7. Exploitation is network-accessible, low complexity, requires low privileges, and requires a victim to view the stored content. Scope changes beyond the vulnerable component; confidentiality and integrity impacts are high, while availability impact is not identified.
Likely exposure
Exposure is most likely where affected Adobe Commerce, Adobe Commerce B2B, or Magento Open Source releases are deployed and low-privileged users can submit content to vulnerable form fields. Internet-facing commerce administration or contributor workflows increase practical concern. Confirm the exact edition, release, patch level, and accessible roles.
Exploitation context
Successful exploitation requires an authenticated low-privileged attacker to store malicious content and a victim to visit the page containing it. The supplied sources do not establish active exploitation, and the record is not listed as KEV. No conclusion should be drawn about exploitation outside the supplied evidence.
Researcher notes
The source bundle identifies affected pre-fix release lines and corresponding unaffected boundary releases across Adobe Commerce, Commerce B2B, and Magento Open Source. The prose description and structured version entries use different boundary notation, so analysts should use APSB26-05 to resolve edition-specific applicability. No exploit methodology or confirmed in-the-wild activity is provided.
Mitigation direction
Review Adobe advisory APSB26-05 and upgrade to the applicable fixed or later supported release.
Prioritize systems where low-privileged accounts can populate fields later viewed by administrators or customers.
Restrict unnecessary low-privileged accounts and form-field access until remediation is complete.
After upgrading, invalidate potentially exposed sessions according to organizational incident-response policy.
Validation and detection
Inventory Adobe Commerce, Commerce B2B, and Magento Open Source editions and exact patch levels.
Compare each deployment against the affected and fixed release information in APSB26-05.
Identify roles permitted to store content in fields later rendered to other users.
Review application and security telemetry for suspicious stored content or unexpected browser-side activity.
Confirm remediation in a safe test environment without executing untrusted scripts.
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.