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 save malicious script content in a vulnerable form field. The script runs when another person views the affected page, potentially exposing limited browser-accessible information or allowing unauthorized actions in that user’s session. The issue requires both authenticated attacker access and victim interaction.
Executive priority
Schedule prompt remediation through normal vulnerability-management processes. Prioritize externally reachable or heavily used AEM environments and systems with broad low-privileged author access. Emergency response is not supported by current exploitation evidence, but stored browser-side code can affect trusted users and should not remain unresolved.
Technical view
CVE-2026-27236 is stored XSS (CWE-79) affecting Adobe Experience Manager 6.5.23 and earlier. CVSS 3.1 is 5.4: network-accessible, low complexity, low privileges required, user interaction required, changed scope, low confidentiality and integrity impact, and no availability impact.
Likely exposure
Exposure is most likely where AEM users with limited privileges can populate vulnerable form fields and other users later view the resulting pages. Internet reachability increases opportunity but does not remove the authentication requirement. The supplied data also identifies Cloud Service and 6.5 LTS release thresholds requiring version verification.
Exploitation context
The CVE is not listed in KEV, and the supplied sources provide no evidence of active exploitation. Abuse requires a low-privileged authenticated attacker to store content and a victim to view the affected page. No public exploit status is established by this source bundle.
Researcher notes
The vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. Changed scope reflects script execution in a victim’s browser security context. The bundle does not identify specific vulnerable fields, affected roles, detection indicators, public proof-of-concept availability, or observed campaigns; consult Adobe APSB26-24 for release-specific guidance.
Mitigation direction
Apply Adobe’s security update appropriate to the deployed AEM release track.
Upgrade AEM 6.5 installations to 6.5.24 or a later non-affected release.
Verify Cloud Service and 6.5 LTS remediation requirements against Adobe APSB26-24.
Restrict low-privileged access to affected content-authoring and form functions until remediation.
Review Adobe guidance before relying on input filtering or other compensating controls.
Validation and detection
Inventory all AEM deployments and record their exact release and service-pack levels.
Flag AEM 6.5.23 and earlier installations as affected.
Compare Cloud Service and 6.5 LTS versions with Adobe APSB26-24.
Confirm patched environments no longer accept unsafe active content in affected fields.
Review recently modified form-field content and relevant security reports for suspicious 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.
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.