Adobe Commerce versions 2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, 2.4.4-p17 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, potentially gaining elevated access or control over the victim's account or session. Scope is changed.
Security readout for executives and security teams
Plain-English summary
A low-privileged user could save malicious script content in a vulnerable field. When another user views the affected page, the script may run with the site's trust, potentially compromising that user's account or session. Administrators and other privileged users could present the greatest business impact.
Executive priority
Treat this as a high-priority remediation because compromise of a privileged viewer could expose customer or administrative data and enable unauthorized account actions. Confirm affected versions promptly and schedule vendor-directed updates according to exposure and account privilege.
Technical view
This is stored cross-site scripting, CWE-79, with CVSS 3.1 score 8.7. Exploitation is network-accessible, low complexity, requires low privileges and victim interaction, and crosses a security boundary. The stated impacts are high confidentiality and integrity loss without direct availability impact.
Likely exposure
Adobe Commerce 2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, 2.4.4-p17, and earlier are identified as affected. The structured record also references Commerce B2B and Magento Open Source, but its version-range encoding is unclear; confirm exact product-specific exposure with Adobe's advisory.
Exploitation context
The supplied record does not identify this CVE as being in KEV and provides no evidence of active exploitation. Successful abuse requires an authenticated low-privileged attacker to store malicious content and another user to view the affected page.
Researcher notes
The CVSS vector is AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N. The affected-version description is clear for Adobe Commerce, while the structured ranges covering Commerce B2B and Magento Open Source are ambiguous in the supplied bundle. No vulnerable field names, routes, public proof of concept, or exploitation telemetry are provided.
Mitigation direction
Review Adobe APSB26-49 for exact product-specific corrected releases and apply the vendor's remediation guidance.
Prioritize internet-facing stores and environments where low-privileged users can submit stored content.
Until remediated, restrict untrusted access to affected submission workflows where operationally feasible.
Investigate suspected injection and reset affected accounts or sessions under established incident-response procedures.
Validation and detection
Inventory exact Adobe Commerce, Commerce B2B, and Magento Open Source editions and versions.
Compare each installation against Adobe APSB26-49 and the CVE record's affected-version information.
Review stored content and security logs for unexpected script-like input or anomalous account activity.
After remediation, confirm deployed versions and safely regression-test relevant forms without executable payloads.
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.