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 attacker to inject malicious scripts into vulnerable form fields. 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 low-privileged attacker can save malicious script content in certain Adobe Commerce form fields. If another user visits the affected page, the script may run in that user’s browser, potentially exposing data or changing actions performed in their session. A victim must visit the page, limiting but not eliminating business risk.
Executive priority
Schedule remediation through the normal security-update process, with faster handling for externally reachable commerce systems accepting low-privileged input. The medium severity, required victim interaction, and lack of cited active exploitation reduce emergency urgency, but stored browser code can still affect trusted staff or customer sessions.
Technical view
CVE-2026-21292 is stored cross-site scripting (CWE-79) with CVSS 3.1 score 5.4. It is network-accessible, low complexity, requires low privileges and victim interaction, and crosses a security boundary. Expected impact is limited confidentiality and integrity loss without availability impact. The supplied narrative identifies Adobe Commerce releases through specified patch levels as affected.
Likely exposure
Exposure is most likely where low-privileged users can submit data to vulnerable form fields and another user later views the stored content. The source bundle does not identify the specific fields, pages, roles, or deployment configurations involved. Confirm exposure using the exact product, edition, branch, and version.
Exploitation context
Exploitation requires a low-privileged attacker to store malicious script content and a victim to browse the affected page. The bundle marks the CVE as absent from KEV and provides no cited evidence of active exploitation. This does not prove exploitation has never occurred.
Researcher notes
The supplied data has presentation ambiguity: its narrative names affected Adobe Commerce versions, while structured ranges also reference Adobe Commerce B2B and Magento Open Source with apparent upper boundaries. Validate edition-specific applicability against APSB26-05. The vulnerable fields and viewing contexts are not identified in the bundle, so do not infer a specific endpoint or role.
Mitigation direction
Inventory Adobe Commerce, Adobe Commerce B2B, and Magento Open Source editions and exact versions.
Review Adobe APSB26-05 and apply Adobe’s applicable security update for each installed product branch.
Follow Adobe’s guidance rather than relying on unverified generic filtering workarounds.
Validation and detection
Compare each deployed edition and version with the CVE record and Adobe advisory.
Confirm the applicable Adobe security update is installed and the resulting version is outside affected boundaries.
Review stored form content for unexpected script-capable markup without rendering or executing it.
Review available audit records for suspicious low-privileged edits to stored form fields.
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.
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.