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 enabling actions with that user’s permissions. Victim interaction is required, and the supplied sources do not indicate service disruption.
Executive priority
Treat as a scheduled, risk-based remediation rather than an emergency outage. Accelerate work where authors can influence pages viewed by administrators, employees, or customers. Confirm ownership, affected versions, privileged viewing workflows, and an update deadline through normal vulnerability-management governance.
Technical view
CVE-2026-27244 is stored cross-site scripting (CWE-79) with CVSS 3.1 score 5.4. Exploitation is network-accessible, low complexity, requires low privileges and victim interaction, and can cross a security boundary. Expected impact is limited confidentiality and integrity loss without availability impact.
Likely exposure
Exposure requires an affected AEM release, a low-privileged account able to populate a vulnerable form field, and a victim who views the stored content. The bundle identifies AEM 6.5.23 and earlier and also reports affected Cloud Service and 6.5 LTS ranges. Confirm exact applicability against Adobe’s advisory.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation. That does not prove exploitation is absent. The attack depends on authenticated, low-privileged content submission and subsequent page viewing, reducing immediacy but creating meaningful risk for administrative or trusted-user sessions.
Researcher notes
The vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. Scope change reflects script execution in a victim’s browser context. The bundle does not identify specific vulnerable fields, detection indicators, exploit availability, or confirmed attacks; testing should remain authorized and non-destructive.
Mitigation direction
Review Adobe APSB26-24 and apply the vendor-supported update for each deployed AEM release line.
Prioritize externally reachable instances and environments where untrusted or numerous users hold content-authoring permissions.
Restrict form-field editing and content-authoring privileges until affected systems are updated.
Use existing content-security controls as defense in depth, not as a substitute for vendor remediation.
Validation and detection
Inventory AEM versions and compare each deployment with the affected ranges in Adobe APSB26-24.
Confirm updated 6.5 deployments are version 6.5.24 or later where applicable.
Confirm Cloud Service and 6.5 LTS release status directly against Adobe’s advisory.
Identify roles able to store content in form fields and verify least-privilege access.
Review stored form content and relevant audit records for unexpected script-like material or unauthorized edits.
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.