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 store malicious JavaScript in an Adobe Experience Manager form field. The script runs when another user visits the affected page, potentially exposing browser-accessible information or causing unauthorized actions. Exploitation requires a victim to view the page.
Executive priority
Treat as a planned, prompt remediation rather than an emergency. Accelerate action where AEM is externally reachable, supports untrusted contributors, or hosts sensitive administrative sessions. Risk is moderated by required attacker privileges and victim interaction, but stored content can repeatedly affect users.
Technical view
CVE-2026-27265 is stored XSS (CWE-79) in Adobe Experience Manager. It is network-accessible, low complexity, requires low privileges and user interaction, and crosses a security boundary. CVSS 3.1 is 5.4, with low confidentiality and integrity impact and no indicated availability impact.
Likely exposure
The description explicitly identifies Adobe Experience Manager 6.5.23 and earlier as affected. Organizations should inventory AEM instances, including authoring and publishing environments. The bundle’s Cloud Service and 6.5 LTS version entries are insufficiently clear to determine their exact affected ranges independently.
Exploitation context
The bundle does not report active exploitation, and the CVE is not identified as being in KEV. This does not prove exploitation is absent. Abuse requires an authenticated low-privileged attacker to save content in a vulnerable field and a victim to visit the resulting page.
Researcher notes
The supplied description clearly covers AEM 6.5.23 and earlier, but the structured Cloud Service and 6.5 LTS entries do not express unambiguous affected-range semantics. Validate those products directly against Adobe’s advisory. No exploit method, proof of concept, or confirmed exploitation is established by the bundle.
Mitigation direction
Check Adobe advisory APSB26-24 for the applicable product-specific update or mitigation.
Prioritize internet-facing and multi-author AEM environments where low-privileged users can submit content.
Restrict untrusted users’ form and content-authoring permissions until remediation is confirmed.
Review stored content for unexpected scripts or suspicious markup.
Validation and detection
Record each AEM deployment’s edition, service model, and exact version.
Compare each deployment against Adobe APSB26-24 rather than inferring Cloud Service or LTS ranges.
Test authorized low-privileged workflows for unsafe stored markup using non-executable test strings.
Review application and audit logs for suspicious content changes around vulnerable fields.
Confirm remediation prevents stored active content from executing in another user’s browser.
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.