CVE-2025-64565VulnerabilityPublished 10 Dec 2025

CVE-2025-64565: Adobe Experience Manager · Cross-site Scripting (DOM-based XSS)

Affects Adobe Experience ManagerSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 08:11 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Adobe Adobe Experience Manager	Affected =0	Fixed in–

AI-suggested

1. Monitor Adobe's official channels for patches addressing CVE-2025-64565 and apply them promptly once released. 2. Implement strict client-side input validation and output encoding to sanitize user-controllable inputs processed by JavaScript in AEM pages, reducing the risk of DOM-based XSS. 3. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and mitigate the impact of injected malicious code. 4. Educate end-users and administrators about the risks of clicking unknown or suspicious links, emphasizing phishing awareness to reduce user interaction exploitation. 5. Regularly audit and review custom client-side scripts and third-party components integrated with AEM for insecure coding practices that could facilitate DOM-based XSS. 6. Use web application firewalls (WAF) with rules tuned to detect and block XSS attack patterns targeting AEM endpoints. 7. Implement multi-factor authentication (MFA) to reduce the impact of stolen session tokens or credentials. 8. Conduct security testing, including penetration testing focused on client-side vulnerabilities, to identify and remediate similar issues proactively.

Description

CVE-2025-64565 is a DOM-based Cross-Site Scripting (XSS) vulnerability affecting Adobe Experience Manager (AEM) versions 6.5.23 and earlier. This vulnerability allows a low-privileged attacker to execute malicious scripts in the context of a victim's browser by tricking the user into interacting with a crafted URL or manipulated web page. Exploitation requires user interaction, such as clicking a link or visiting a malicious page. The vulnerability impacts confidentiality and integrity but does not affect availability. The CVSS score is 5.4 (medium severity), reflecting the need for user interaction and limited privileges required for exploitation. European organizations using AEM for content management and digital experience delivery could be targeted, especially those with public-facing web portals. Mitigation involves applying patches once available, implementing strict input validation and output encoding in client-side scripts, and educating users about phishing risks.

Impact

For European organizations, this vulnerability poses a risk to the confidentiality and integrity of user data accessed through Adobe Experience Manager portals. Attackers exploiting this vulnerability could steal session cookies, enabling account hijacking, or manipulate web content to conduct phishing or fraud. This can damage organizational reputation, lead to regulatory non-compliance under GDPR due to data breaches, and disrupt customer trust. Since AEM is commonly used by government agencies, financial institutions, and large enterprises in Europe for content management and digital marketing, the impact could be significant if exploited. The requirement for user interaction limits automated exploitation but does not eliminate risk, especially in environments with high user traffic or where social engineering is effective. The vulnerability does not affect system availability, so denial-of-service is not a concern here. However, the potential for lateral movement or privilege escalation through stolen credentials or session tokens could increase the overall risk profile.

Summary

CVE-2025-64565 is a DOM-based Cross-Site Scripting vulnerability identified in Adobe Experience Manager (AEM) versions 6.5.23 and earlier. This vulnerability arises from improper handling of client-side scripts that process user-controllable input, allowing an attacker to inject malicious JavaScript code that executes within the victim's browser context. The attack vector requires a low-privileged attacker to craft a malicious URL or web page that, when visited or interacted with by a user, triggers the execution of the injected script. This can lead to the theft of sensitive information such as session tokens, cookies, or other confidential data accessible via the browser, and potentially allow the attacker to perform actions on behalf of the victim within the affected web application. The vulnerability is classified under CWE-79, indicating a Cross-Site Scripting flaw, and is DOM-based, meaning the vulnerability exists in client-side code rather than server-side. The CVSS 3.1 base score of 5.4 reflects a medium severity, considering the attack complexity is low, but user interaction is required, and the attacker must have some privileges. The scope is changed (S:C), indicating that exploitation can affect components beyond the vulnerable code. No patches were linked at the time of publication, and no known exploits have been reported in the wild. Adobe Experience Manager is widely used by enterprises for managing digital content and customer experiences, making this vulnerability relevant for organizations relying on AEM for their web presence and digital services.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

helpx.adobe.com/security/products/experience-manager/apsb25-115.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Dec 2025, 20:59 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats