Adobe Experience Manager
CVE-2025-64790
MEDIUM
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege AEM author account
-
DeliveryInject malicious script into vulnerable form field
-
ExploitVictim browses to affected page
-
ExecutionStored payload executes in victim browser
-
ImpactHijack victim session / act as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid low-privileged authenticated account on the AEM instance (PR:L) with permission to submit or edit the vulnerable form fields, plus a victim who subsequently browses to the page rendering the injected field (UI:R). The payload is stored and executes in the victim's browser context (scope change S:C, crossing from the attacker's input into the victim's session). Limiting factors: no unauthenticated path, no server-side code execution, no availability impact, and success depends on a higher-value victim actually viewing the affected page. Affects Adobe Experience Manager 6.5.23 and earlier, AEM Cloud Service, and AEM 6.5 LTS. |
| Impact | This is a classic high-CVSS-context-but-low-real-risk issue. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, 5.4 MEDIUM) confirms a doubly-gated stored XSS: the attacker must already hold a low-privilege authenticated account (PR:L) AND a victim must browse to the page containing the injected field (UI:R). Impact is limited to C:L/I:L with no availability impact - script execution in the victim's browser session, not server compromise. Exploitation signals are weak and consistent: EPSS is 0.25% (15th percentile), there is no CISA KEV listing, and no public exploit code was identified. No signals conflict here - the low EPSS, absence of KEV, and MEDIUM CVSS all agree this is not an urgent priority. The realistic risk is targeted, not widespread: a malicious insider or a compromised low-priv author account escalating to steal a higher-privileged user's session within the AEM authoring environment. Patch this on a normal cadence via APSB25-115; it is not a drop-everything emergency. |
| Exploit ScenarioDerived | A low-privileged AEM author account injects a malicious JavaScript payload into a vulnerable form field. When a higher-privileged user (e.g., an editor or administrator) later browses to the page rendering that field, the script executes in their authenticated browser session, enabling session/cookie theft or actions on their behalf. No public POC or active exploitation has been identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 26, 2026
Stored cross-site scripting in Adobe Experience Manager (AEM) 6.5.23 and earlier, AEM 6.5 LTS, and AEM Cloud Service lets an attacker with a valid low-privileged account persist malicious JavaScript inside vulnerable form fields; the script then executes in the browser of any higher-privileged user who views the affected page. The author-input prerequisite (PR:L) and the requirement that a victim navigate to the poisoned page (UI:R) substantially limit practical impact, no server-side code execution or availability loss is possible, and no public exploit has been identified at time of analysis. EPSS is 0.25% (15th percentile), consistent with a low-likelihood, targeted-abuse scenario rather than mass exploitation.
RemediationAI
Apply the fixed release identified in Adobe security bulletin APSB25-115 (https://helpx.adobe.com/security/products/experience-manager/apsb25-115.html); Adobe AEM Cloud Service customers generally receive the remediation automatically as part of the managed service, while on-premise 6.5 and 6.5 LTS deployments must be upgraded off 6.5.23 and earlier per the bulletin's version guidance. Because exploitation requires an authenticated author-level account, reducing the attack surface is effective interim mitigation: audit and tighten author permissions so only trusted users can create or edit the affected form fields, and remove or restrict unused form components. Deploy Dispatcher or reverse-proxy input filtering and a strict Content-Security-Policy (script-src restricted to trusted origins, no unsafe-inline) on render paths to blunt stored payload execution, accepting that CSP may break legitimate inline scripts in existing AEM components and requires testing. Restrict access to AEM author instances to trusted networks or VPN, which prevents low-privileged external accounts from injecting content but does not protect against malicious insiders. WAF signatures targeting script injection in form submissions can add a layer of detection, though they are bypassable and should not be treated as a substitute for patching.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The defect is a classic CWE-79 improper neutralization of user-supplied input during web page generation, here in its stored (persistent) variant. AEM form components accept and persist field content, and the application fails to adequately encode or sanitize that content before it is rendered back into the HTML response. Because the payload is stored server-side, it does not depend on the victim clicking a crafted link - only on the victim loading the page that renders the tainted field. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N reflects network reachability of the authoring/publishing interface, low privileges required to submit or edit form content, required victim interaction, and a scope change (S:C) because execution moves from the attacker's stored input into the victim's browser session. Confidentiality and integrity impacts are low, and the absence of an availability component indicates no denial-of-service dimension. Affected product identifiers include cpe:2.3:a:adobe:experience_manager with the 6.5 LTS channel, the AEM Cloud Service channel, and unversioned 6.5.x ranges, meaning both on-premise 6.5 deployments (6.5.23 and earlier) and managed cloud instances are in scope.
Know when Experience Manager gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Network-reachable authoring UI (AV:N), needs a low-priv account (PR:L) and victim page view (UI:R); stored XSS crosses into victim browser (S:C) with limited C:L/I:L and no availability impact.
Primary rating from Vendor (adobe).
CVSS VectorVendor: adobe
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
Affected Products (CPE)CVE.org
More in Experience Manager
View allSitecore Experience Manager, Platform, and Commerce versions 9.0 through 10.4 contain a Zip Slip vulnerability that allo
Sitecore PowerShell Extensions through version 7.0 allows authenticated users to upload arbitrary files including ASPX w
Dispatcher before 4.1.5 in Adobe Experience Manager 5.6.1, 6.0.0, and 6.1.0 does not properly implement a URL filter, wh
Adobe Experience Manager versions 6.5.23.0 and earlier contain a deserialization of untrusted data vulnerability that al
Sitecore Experience Manager (XM) and Experience Platform (XP) versions 10.1 through 10.4.1 contain a hardcoded administr
The Servlets Post component 2.3.6 in Apache Sling, as used in Adobe Experience Manager 5.6.1, 6.0.0, and 6.1.0, allows r
Multiple Sitecore products allow remote code execution. Rated critical severity (CVSS 9.8), this vulnerability is remote
Adobe Experience Manager 6.2 and earlier has a malicious file execution vulnerability. Rated critical severity (CVSS 9.8
Adobe Experience Manager versions 6.5.23.0 and earlier are affected by a Server-Side Request Forgery (SSRF) vulnerabilit
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Sitecore Sitecore Experience Manager (XM), S
An issue was discovered in Sitecore Experience Platform (XP), Experience Manager (XM), and Experience Commerce (XC) 8.0
An issue in the MVC Device Simulator of Sitecore Experience Platform (XP), Experience Manager (XM), and Experience Comme
NVD
CVE.org
EPSS
VulDB
GitHub PoC
Exploit-DB