Adobe Experience Manager versions 6.5.23 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by an 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
An authenticated, lower-privileged attacker could save malicious JavaScript in an Adobe Experience Manager form field. The script may run when another user visits the affected page, potentially exposing or altering limited browser-accessible information. A victim must open the page; availability is not affected according to the CVSS assessment.
Executive priority
Schedule timely remediation and prioritize externally reachable AEM environments where lower-privileged users can create content viewed by employees or administrators. The moderate rating reflects limited confidentiality and integrity impact, required authentication, and required victim interaction—not an absence of risk.
Technical view
CVE-2026-27226 is stored cross-site scripting (CWE-79) with CVSS 3.1 score 5.4. Exploitation is network-accessible, low complexity, requires low privileges and user interaction, and crosses a security boundary. The supplied description identifies AEM 6.5.23 and earlier as affected.
Likely exposure
Organizations running AEM 6.5.23 or earlier should assess exposure, especially where lower-privileged accounts can populate form fields viewed by other users. Structured data also references Cloud Service and 6.5 LTS boundaries, but their precise inclusivity is unclear in the bundle.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not identified as being in KEV. Exploitation requires an attacker with low privileges to store content and a victim to visit the affected page. No unauthenticated or availability impact is indicated.
Researcher notes
The structured affected data lists boundary pairs for AEM Cloud Service, 6.5 LTS, and 6.5 without clearly explaining inclusivity. The narrative explicitly states 6.5.23 and earlier. Confirm exact affected and fixed releases against APSB26-24 before making fleet-wide exposure determinations.
Mitigation direction
Inventory AEM deployments and compare installed versions with Adobe APSB26-24.
Apply the vendor-recommended update or remediation identified in Adobe's advisory.
Temporarily restrict untrusted accounts from editing relevant form fields where operationally feasible.
Review stored form-field content and remove confirmed malicious entries through normal administrative controls.
Validation and detection
Confirm whether each AEM deployment is version 6.5.23 or earlier.
Check Adobe's advisory for exact Cloud Service and 6.5 LTS affected boundaries.
Identify accounts permitted to store content in relevant form fields.
Review content changes and security telemetry for unexpected script-like field content.
After remediation, verify the installed release and perform authorized, non-destructive regression testing.
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.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
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.