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) 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.
Security readout for executives and security teams
Plain-English summary
A highly privileged attacker could store malicious JavaScript in an Adobe Commerce form field. When another user views the affected page, the script may run in their browser and enable session takeover. This could expose sensitive information or permit unauthorized actions, but exploitation requires both privileged access and victim interaction.
Executive priority
Treat as a high-priority remediation for customer-facing or sensitive commerce systems. The privilege prerequisite reduces opportunistic risk, but session takeover could produce serious data exposure or unauthorized administrative activity. Accelerate action where privileged accounts are numerous, shared, externally accessible, or suspected compromised.
Technical view
CVE-2026-21361 is a stored cross-site scripting vulnerability (CWE-79) with CVSS 3.1 score 8.1. It is network-accessible, low-complexity, requires high privileges and user interaction, and changes security scope. Successful exploitation can cause high confidentiality and integrity impact without direct availability impact.
Likely exposure
Prioritize internet-facing or business-critical Adobe Commerce deployments on the listed affected branches, especially where multiple users hold privileged content-management access. The bundle also names Adobe Commerce B2B and Magento Open Source, but its serialized version ranges are ambiguous; confirm exact applicability against Adobe's advisory.
Exploitation context
The attacker must already possess high privileges and inject script into a vulnerable form field. A victim must then visit the page containing that field. The bundle marks this CVE as not in KEV and provides no evidence of active exploitation; that does not prove exploitation is absent.
Researcher notes
The supplied description lists Adobe Commerce releases through 2.4.8-p3, 2.4.7-p8, 2.4.6-p13, 2.4.5-p15, and 2.4.4-p16 as affected. The structured product/version entries appear to identify later boundaries but are not unambiguous. Use APSB26-05 as the authoritative applicability and remediation reference.
Mitigation direction
Apply Adobe's applicable security update for the deployed product and release branch.
Restrict privileged administrative access while remediation is pending.
Review privileged accounts and revoke unnecessary permissions.
Check Adobe's advisory when version applicability or upgrade targets are unclear.
Validation and detection
Inventory Adobe Commerce, Commerce B2B, and Magento Open Source versions.
Compare each deployment and release branch with Adobe advisory APSB26-05.
Review privileged account activity and recent changes to administrative form fields.
After updating, confirm installed versions and rerun approved defensive security testing.
Investigate suspicious browser sessions or administrative actions around modified content.
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.