Adobe Experience Manager versions 6.5.23 and earlier are 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.
Security readout for executives and security teams
Plain-English summary
Adobe Experience Manager 6.5.23 and earlier can retain attacker-supplied JavaScript in vulnerable form fields. When another user views the affected page, the script may run in that user’s browser, potentially exposing data or enabling unauthorized actions within the user’s session.
Executive priority
Treat this as a planned, near-term remediation rather than an emergency outage. Accelerate work for internet-facing systems or workflows where untrusted contributors can place content before privileged users. Investigate promptly if suspicious stored content or browser activity is detected.
Technical view
This is stored cross-site scripting (CWE-79) with CVSS 3.1 score 5.4. Exploitation requires network access, low privileges, and victim interaction. Successful exploitation can cross a security boundary and cause limited confidentiality and integrity impact, but the supplied vector indicates no availability impact.
Likely exposure
Prioritize AEM 6.5.23 and earlier, especially deployments where low-privileged users can submit content to form fields viewed by administrators, authors, or customers. The supplied structured version data also names Cloud Service and 6.5 LTS boundaries, but does not clearly describe their interval semantics.
Exploitation context
The source bundle provides no evidence of active exploitation, and the CVE is not identified as being in CISA KEV. Exploitation is not unauthenticated: it requires low privileges to store malicious content and a victim to view the affected page.
Researcher notes
The CVSS vector is AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. The supplied narrative clearly identifies AEM 6.5.23 and earlier. Structured affected data names 6.5.24, Cloud Service 2026.2.0, and 6.5 LTS SP2 boundaries, but lacks explicit range operators; validate exact applicability through APSB26-24.
Mitigation direction
Consult Adobe advisory APSB26-24 and apply the supported update appropriate to your AEM deployment.
Restrict form-field submission and content-authoring permissions to necessary, trusted roles.
Review input validation and output encoding around user-controlled form content.
Limit privileged users from reviewing untrusted submissions until remediation is confirmed.
Validation and detection
Inventory AEM deployments and identify instances running version 6.5.23 or earlier.
Confirm installed remediation status against Adobe advisory APSB26-24.
Identify roles able to populate form fields later rendered to other users.
Verify untrusted field content cannot execute as script in a controlled test environment.
Review content and security telemetry for suspicious stored scripts or unexpected browser activity.
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.