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 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. Scope is changed.
Security readout for executives and security teams
Plain-English summary
A highly privileged user could save malicious script content in certain Adobe Commerce form fields. The script may later run when another user views the affected page, potentially exposing or changing limited browser-accessible information. The victim must visit the page, and the flaw does not directly affect availability.
Executive priority
Schedule prompt remediation through normal vulnerability-management processes. Prioritize internet-facing commerce systems, environments handling sensitive sessions, and deployments with weak privileged-account controls. Emergency action is not supported by the supplied evidence, but delayed remediation leaves a persistent browser-based attack path available to privileged or compromised accounts.
Technical view
CVE-2026-34658 is stored XSS (CWE-79) with CVSS 3.1 score 4.8. Exploitation is network-accessible with low complexity, but requires high privileges and victim interaction. Successful exploitation changes security scope and may cause low confidentiality and integrity impact, with no stated availability impact.
Likely exposure
Exposure is most likely where an affected Adobe Commerce release remains deployed and high-privileged accounts can populate vulnerable fields. The description identifies 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 as affected.
Exploitation context
No active exploitation is established by the supplied sources, and the CVE is not identified as KEV. Abuse requires a high-privileged attacker to store content and a victim to view the affected page. These prerequisites reduce broad opportunistic risk, but compromised privileged accounts could make exploitation practical.
Researcher notes
The source bundle’s structured version entries are difficult to interpret and appear to include later release boundaries. Use Adobe APSB26-49 as the authoritative version and remediation reference. Testing should focus on stored input reaching browser-rendered contexts, output encoding, privilege requirements, and victim interaction without executing active scripts.
Mitigation direction
Check the deployed product and version against Adobe advisory APSB26-49.
Upgrade to the applicable vendor-designated fixed release described by Adobe.
Restrict and review high-privileged accounts until remediation is complete.
Monitor privileged changes to form fields and investigate unexpected script-like content.
Validation and detection
Inventory Adobe Commerce, Commerce B2B, and Magento Open Source versions in scope.
Confirm installed patch levels against Adobe APSB26-49.
Review vulnerable-field handling using harmless, non-executable test content in an authorized environment.
Check logs and content histories for unexpected privileged field modifications.
Verify stored values are safely encoded when rendered in browsers.
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.