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.
Security readout for executives and security teams
Plain-English summary
A remote attacker could store malicious browser code in certain Adobe Commerce form fields. When another user visits the affected page, that code may run with the user’s privileges, potentially exposing sensitive information or enabling account or session control. The vulnerability is rated critical, but the supplied sources do not report active exploitation.
Executive priority
Treat this as an accelerated remediation priority, especially for Internet-facing commerce systems and pages viewed by administrators. Confirm exposure immediately and follow Adobe’s advisory. Consider incident investigation if suspicious stored content or account activity is found.
Technical view
CVE-2026-76200 is stored cross-site scripting (CWE-79) with CVSS 3.1 score 9.3. The vector indicates network access, low complexity, no attacker privileges, required victim interaction, changed scope, and high confidentiality and integrity impact. Availability impact is not identified. Specific vulnerable fields and application paths are not provided.
Likely exposure
Organizations using the listed Adobe Commerce, Adobe Commerce B2B, or Magento Open Source release families may be exposed. Internet-accessible deployments and privileged users increase potential business impact. The supplied version-range formatting is ambiguous, so administrators should verify exact affected and corrected versions against Adobe APSB26-138.
Exploitation context
An attacker must inject content into a vulnerable field and induce a victim to view the page containing it. No attacker privileges are indicated, but victim interaction is required. The bundle marks this CVE as not present in KEV and provides no evidence of active exploitation.
Researcher notes
The source bundle does not identify vulnerable fields, affected routes, remediation details, or exploitation telemetry. Its version data appears compacted and should not be independently interpreted as precise range syntax. Defensive validation should focus on stored-input rendering and privilege context without testing production systems destructively.
Mitigation direction
Compare every deployed product and version with Adobe APSB26-138.
Apply the vendor-supported remediation or corrected release identified by Adobe after appropriate testing.
Restrict untrusted access to affected form surfaces where operationally feasible.
Monitor stored content and account activity for suspicious scripts or session misuse.
Validation and detection
Inventory Adobe Commerce, Commerce B2B, and Magento Open Source versions across all environments.
Confirm affected and corrected version boundaries directly against Adobe APSB26-138.
Use approved non-production testing to verify stored input is safely encoded when rendered.
Review application content, logs, and session activity for indicators of prior injection.
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.