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 AEM user could store malicious JavaScript in a vulnerable form field. The script may run when another user visits the affected page, potentially exposing browser-accessible information or allowing limited actions as that user. Exploitation requires both authenticated low-level access and victim interaction.
Executive priority
Schedule prompt remediation through normal vulnerability-management processes. Internet-facing or broadly shared authoring environments deserve earlier attention, especially where many low-privileged contributors can edit forms. This is not an emergency-level issue based on the supplied evidence, but stored XSS can enable targeted compromise of privileged users.
Technical view
CVE-2026-27237 is stored XSS (CWE-79) in Adobe Experience Manager 6.5.23 and earlier. It is remotely reachable, low complexity, requires low privileges and user interaction, and crosses a security boundary. CVSS 3.1 is 5.4: AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N.
Likely exposure
Exposure is most likely where AEM 6.5.23 or earlier permits low-privileged users to populate vulnerable form fields and other users subsequently view those pages. The bundle’s structured version data also mentions Cloud Service and 6.5 LTS, but does not clearly establish their affected ranges.
Exploitation context
The supplied evidence does not establish active exploitation, and this CVE is not identified as KEV. Abuse requires a low-privileged attacker to persist script content and a victim to browse the affected page. Impact is limited to low confidentiality and integrity loss, with no availability impact stated.
Researcher notes
The attack chain depends on persistent input reaching a browser without adequate neutralization. Researchers should map affected form fields, authorization boundaries, output contexts, and victim roles without using live payloads. The bundle clearly identifies AEM 6.5.23 and earlier, while its Cloud Service and LTS version entries are insufficiently explicit for definitive scoping.
Mitigation direction
Inventory AEM deployments and identify installations running version 6.5.23 or earlier.
Review Adobe advisory APSB26-24 and apply the vendor-prescribed update for each deployment model.
Restrict low-privileged access to affected form-authoring functions until remediation is complete.
Review stored form content for unexpected scripts or suspicious markup.
Validation and detection
Confirm deployed AEM versions using authoritative asset and deployment records.
Verify remediated versions against Adobe APSB26-24 rather than relying solely on the bundle’s ambiguous ranges.
Test relevant form fields for safe output handling in an authorized non-production environment.
Review application and audit logs for suspicious form changes by low-privileged accounts.
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.