Adobe Experience Manager versions 6.5.23 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.
Security readout for executives and security teams
Plain-English summary
Adobe Experience Manager 6.5.23 and earlier contain a stored cross-site scripting flaw. A low-privileged attacker could save malicious JavaScript in a vulnerable form field. The script may run when another user views the affected page, potentially exposing browser-accessible information or allowing actions in that user’s session.
Executive priority
Treat this as a planned, near-term remediation rather than an emergency. Accelerate work for internet-facing authoring workflows, large low-privileged user populations, or sensitive administrative viewers. The absence of reported active exploitation lowers immediate urgency but does not eliminate browser-session risk.
Technical view
CVE-2026-27266 is a stored XSS vulnerability classified as CWE-79. It is remotely reachable, requires low privileges and victim interaction, and can cross a security boundary. CVSS 3.1 scores it 5.4, with limited confidentiality and integrity impact and no stated availability impact.
Likely exposure
Exposure is confirmed for Adobe Experience Manager 6.5.23 and earlier where untrusted low-privileged users can submit content through vulnerable form fields. The supplied version data also mentions Cloud Service and 6.5 LTS, but its range semantics are unclear; verify those deployments against Adobe’s advisory.
Exploitation context
The attacker must possess low-level privileges and persist script content in a vulnerable field. A victim must then visit the page containing that field. The bundle does not report public exploitation, and the CVE is not identified as being in CISA KEV.
Researcher notes
The scope-changing CVSS vector reflects impact beyond the vulnerable component’s security authority. Successful exploitation requires authenticated low privileges plus a viewing user. The supplied bundle does not identify the exact vulnerable fields, component, patch mechanics, or exploitation evidence. Avoid extending affected-version conclusions beyond Adobe’s published advisory.
Mitigation direction
Review Adobe advisory APSB26-24 and apply the vendor-recommended update for each deployed AEM release.
Prioritize instances allowing low-privileged or externally managed users to create form content.
Restrict unnecessary content-authoring permissions until affected systems are updated.
Monitor vendor guidance for Cloud Service and 6.5 LTS applicability.
Validation and detection
Inventory deployed AEM editions and exact versions, including Cloud Service and 6.5 LTS.
Identify forms and workflows accepting stored content from low-privileged users.
Confirm installed versions are outside Adobe’s affected range using APSB26-24.
Review stored form content and browser-side security alerts for suspicious scripts.
Verify least-privilege controls for accounts permitted to create or modify content.
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.