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
A low-privileged user could save malicious JavaScript in certain Adobe Experience Manager form fields. When another user opens the affected page, the script may run in that user’s browser, potentially exposing data or enabling unauthorized actions within their session. Exploitation requires victim interaction.
Executive priority
Prioritize remediation on externally reachable systems or environments allowing broad low-privileged content submission. This is not presented as an emergency or actively exploited issue, but stored XSS can affect higher-privileged viewers. Schedule prompt patching and verify permissions while awaiting or applying the appropriate Adobe update.
Technical view
CVE-2026-27240 is stored cross-site scripting (CWE-79) in Adobe Experience Manager. It is remotely reachable, low complexity, requires low privileges and user interaction, and can cross a security boundary. CVSS 3.1 is 5.4, with low confidentiality and integrity impact and no stated availability impact.
Likely exposure
Exposure is most likely where untrusted or low-privileged users can submit content through vulnerable AEM form fields and other users subsequently view it. The bundle explicitly describes AEM 6.5.23 and earlier; it also lists Cloud Service and 6.5 LTS release boundaries that require confirmation against Adobe’s advisory.
Exploitation context
The source bundle does not identify public exploitation, and the CVE is not listed as KEV. A successful attack requires authenticated low-privileged access plus a victim viewing the stored content. Treat internet-accessible authoring or content-submission workflows as higher exposure, but do not assume compromise without evidence.
Researcher notes
The supplied version data is not fully self-explanatory: the narrative identifies 6.5.23 and earlier, while structured entries include Cloud Service 2026.2.0, 6.5 LTS SP2, and 6.5.24 boundaries. Confirm exact affected and fixed semantics in APSB26-24. No vulnerable field names, proof of concept, or exploitation telemetry are provided.
Mitigation direction
Review Adobe advisory APSB26-24 and apply the vendor-recommended fixed release for your AEM deployment track.
Restrict form submission and content-authoring privileges to trusted users until remediation is complete.
Limit access to AEM authoring interfaces using existing network and identity controls.
Review stored form content for unexpected scripts or suspicious markup.
Validation and detection
Inventory AEM deployment tracks and exact versions, including Cloud Service, 6.5 LTS, and 6.5 installations.
Compare each deployed version with the affected and fixed boundaries documented in APSB26-24.
Confirm low-privileged roles cannot persist executable JavaScript in affected form fields after remediation.
Review application and audit logs for suspicious content changes followed by victim page access.
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.