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 Adobe Experience Manager user could save malicious JavaScript in a vulnerable form field. The script may run when another user views the affected page, potentially exposing browser-accessible information or allowing limited actions in that user’s session. Exploitation requires both authenticated low-level access and victim interaction.
Executive priority
Treat this as a planned but prompt remediation item. Accelerate action for internet-accessible authoring systems or workflows where low-privileged contributors can place content before privileged users. Current evidence does not justify emergency incident status by itself.
Technical view
CVE-2026-27228 is stored XSS (CWE-79) with CVSS 3.1 score 5.4. It is network-reachable, low complexity, requires low privileges and user interaction, changes security scope, and has low confidentiality and integrity impact without availability impact. The description explicitly identifies AEM 6.5.23 and earlier.
Likely exposure
Organizations running AEM 6.5.23 or earlier should assess exposure, especially where low-privileged users can submit content later viewed by editors or administrators. The structured affected data also lists AEM Cloud Service and 6.5 LTS boundaries, but the supplied representation does not clearly express their affected ranges.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not listed as KEV. Abuse requires a low-privileged attacker to store script content and a victim to visit the resulting page. Higher-value sessions could increase business impact.
Researcher notes
The main description explicitly covers AEM 6.5.23 and earlier. Structured entries reference Cloud Service through 2026.2.0, 6.5 LTS through SP2, and 6.5 through 6.5.24 with default unaffected, but their flattened status semantics are ambiguous. Confirm exact affected and fixed boundaries in Adobe APSB26-24.
Mitigation direction
Review Adobe advisory APSB26-24 for product-specific fixed versions and deployment instructions.
Upgrade AEM 6.5 installations from 6.5.23 or earlier to Adobe’s applicable fixed release.
Prioritize environments where untrusted or low-privileged users can submit content.
Restrict unnecessary content-authoring access while remediation is pending.
Validation and detection
Inventory AEM product variants and exact deployed versions.
Confirm whether low-privileged users can populate fields rendered to other users.
Verify remediation status against the version boundaries in Adobe APSB26-24.
Test authorized form workflows for safe output handling after updating.
Review relevant application logs for suspicious stored content, without assuming exploitation.
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.