Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach vulnerable form field over network
-
DeliverySubmit crafted JavaScript payload
-
ExploitPayload stored server-side
-
ExecutionVictim loads page rendering field
-
PersistScript executes in victim session
-
ImpactHijack account or session tokens
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to reach and submit data into a specific vulnerable form field on an Adobe Commerce / Magento Open Source / Adobe Commerce B2B instance (network-reachable, no attacker authentication per CVSS PR:N), and - critically - a victim must subsequently browse to the page that renders the stored field (CVSS UI:R). The limiting factors are this required victim interaction and the need for the target to run an unpatched build at or below the listed 2026-aug versions; impact is highest when the victim is a privileged admin, which the scope-changed vector reflects. |
| Impact | The signals are mixed: CVSS 9.3 is high and PR:N/AV:N/AC:L point to easy, network-reachable, unauthenticated injection, but UI:R meaningfully limits impact because a victim must visit the page containing the stored payload - this is not a fully automatable, wormable flaw. There is no EPSS score, no CISA KEV listing, and no known public POC in the provided data, so there is no evidence of active exploitation; the 9.3 is driven largely by the scope change plus C:H/I:H (session/account compromise) rather than by demonstrated real-world weaponization. Adobe Commerce is a high-value, internet-facing e-commerce target where admin-session XSS can escalate to store compromise and payment/customer-data exposure, so patching should be prioritized even absent exploitation evidence; a mid-sized retail operator with a public storefront should treat this as urgent given the low attack complexity, while acknowledging the UI:R gate as a mitigating factor. |
| Exploit ScenarioDerived | An attacker submits a form field (e.g., a customer- or content-facing input) containing a crafted JavaScript payload, which the platform stores. When a store administrator or another user later opens the page rendering that field, the script executes in their authenticated session and exfiltrates session tokens or performs actions as that user, enabling account or session takeover. No public exploit code is identified at time of analysis, and success depends on a victim loading the affected page (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 08, 2026
Stored cross-site scripting in Adobe Commerce, Magento Open Source, and Adobe Commerce B2B (versions through the August 2026 builds of 2.4.4-2.4.9 / B2B 1.3.3-1.5.3) lets an attacker persist malicious JavaScript into vulnerable form fields that later executes in a victim's browser. Because the CVSS scope is changed, the injected script runs beyond the injection context and can hijack the victim's session or account, and CVSS:3.1 PR:N indicates the injection requires no attacker authentication while UI:R means a victim must load the affected page. No public exploit is identified at time of analysis, and the flaw was reported privately by Adobe PSIRT under APSB26-138.
RemediationAI
Apply the fixed builds released in Adobe Security Bulletin APSB26-138 (https://helpx.adobe.com/security/products/magento/apsb26-138.html); Adobe distributes these as the corresponding security-patched releases/quality patches for the 2.4.x Commerce/Magento Open Source lines and the 1.x B2B line, so upgrade each affected instance to the vendor-designated patched version for its branch. The input does not name a single exact numeric fix build beyond the advisory, so consult APSB26-138 for the precise target version per product line. As compensating controls until patched, tighten the platform's Content Security Policy to restrict inline script execution (Magento supports CSP allowlisting, though overly strict policies can break custom themes/extensions), place the admin panel behind IP allowlisting or a VPN to reduce who can trigger stored payloads, and review/validate the specific form fields for unexpected script content; these reduce but do not eliminate exposure and are not a substitute for the patch.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), a classic stored/persistent XSS in the PHP-based Magento/Adobe Commerce e-commerce platform. Attacker-supplied content submitted through a form field is stored server-side and later rendered without adequate output encoding or sanitization, so the browser interprets it as executable script. The scope-changed CVSS vector (S:C) reflects that the payload executes in a security context different from the one hosting the vulnerable field - typically a privileged admin or another user's authenticated session - which is why session/account takeover is in scope. No CPE strings were provided in the input; affected products are enumerated from the ENISA EUVD version data rather than NVD CPE.
Know when Commerce gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Network-reachable unauthenticated injection (PR:N/AV:N/AC:L) requiring victim page load (UI:R); scope-changed script executes in a privileged session (S:C, C:H/I:H), no availability impact.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
Adobe Commerce is affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by an 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.
Articles & Coverage 1
Executive ViewAI
Adobe Commerce and Magento Open Source versions 2.4.4-2.4.9 contain a stored cross-site scripting vulnerability that allows unauthenticated attackers to inject persistent malicious code into form fields, which then executes in customer browsers with scope to hijack sessions and compromise accounts. No patch is currently available; any organization running affected builds faces immediate risk of customer account takeover and credential theft.
No vendor-released patch identified at time of analysis. Interim mitigations: deploy Web Application Firewall rules to detect and block XSS payloads in vulnerable form fields; enforce strict Content Security Policy (CSP) headers; enhance input validation and output encoding; restrict form access to authenticated users only if operationally feasible; implement session invalidation monitoring to detect hijacking attempts; perform regular user activity audits for signs of unauthorized access.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Privilege escalation in Adobe Commerce and Magento Open Source (including Adobe Commerce B2B) lets a remote attacker gai
Adobe Commerce versions 2.4.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier are affected by an Improper Restriction of XML E
SAP Commerce, versions - 1808, 1811, 1905, 2005, 2011, Backoffice application allows certain authorized users to create
SAP Commerce Cloud, versions - 1808,1811,1905,2005,2011, enables certain users with required privileges to edit drools r
Adobe Commerce versions 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier are affected by an Improper Authentication v
Adobe Commerce versions 2.4.7, 2.4.6-p5, 2.4.5-p7, 2.4.4-p8 and earlier are affected by an Improper Access Control vulne
Adobe Commerce versions 2.4.3-p2 (and earlier), 2.3.7-p3 (and earlier) and 2.4.4 (and earlier) are affected by an Improp
If configured to use an Oracle database and if a query is created using the flexible search java api with a parameterize
SAP Commerce, versions - 6.7, 1808, 1811, 1905, and SAP Commerce (Data Hub), versions - 6.7, 1808, 1811, 1905, allows an
Adobe Commerce versions 2.4.6-p3, 2.4.5-p5, 2.4.4-p6 and earlier are affected by a stored Cross-Site Scripting (XSS) vul
Stored cross-site scripting in Adobe Commerce, Magento Open Source, and Adobe Commerce B2B lets a remote attacker persis
Adobe Commerce versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by an Incorrect A
EUVD-2026-74037
GHSA-w3wg-3rqw-c88m
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB