CVE-2025-64560VulnerabilityPublished 10 Dec 2025

CVE-2025-64560: 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, 06:26 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. Apply patches or updates from Adobe as soon as they become available to address CVE-2025-64560. 2. Implement strict input validation and sanitization on all user-controllable inputs within AEM to prevent injection of malicious scripts into the DOM. 3. Deploy Content Security Policy (CSP) headers to restrict the execution of untrusted scripts and reduce the impact of potential XSS attacks. 4. Conduct regular security assessments and code reviews focusing on client-side scripting and DOM manipulation within AEM implementations. 5. Educate users and administrators about the risks of interacting with suspicious links or content to reduce the likelihood of successful social engineering. 6. Monitor web application logs and user activity for unusual behavior that could indicate exploitation attempts. 7. Consider implementing web application firewalls (WAF) with rules tailored to detect and block XSS payloads targeting AEM. 8. Limit the privileges of users and services interacting with AEM to minimize potential damage from compromised accounts.

Description

CVE-2025-64560 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 and does not allow direct system compromise but can lead to information disclosure and session hijacking. The CVSS score is 5.4 (medium severity), reflecting limited impact on confidentiality and integrity, no impact on availability, and the need for user interaction and low privileges. No known exploits are currently reported in the wild. European organizations using AEM should prioritize patching and implement strict input validation and Content Security Policies to mitigate risk. Countries with significant digital services relying on AEM, such as Germany, France, and the UK, are more likely to be affected due to market penetration and strategic importance of affected targets.

Impact

For European organizations, the impact of CVE-2025-64560 can be significant in terms of confidentiality and integrity of user data. Exploitation could allow attackers to hijack user sessions, steal authentication tokens, or perform actions on behalf of users, potentially leading to unauthorized access to sensitive information or manipulation of business-critical workflows. Although availability is not directly impacted, the reputational damage and potential regulatory consequences under GDPR for data breaches involving personal data could be severe. Organizations relying on Adobe Experience Manager for content management and digital experience delivery, especially those in sectors like finance, government, healthcare, and e-commerce, face increased risk. The requirement for user interaction means that phishing or social engineering could be vectors for exploitation, necessitating user awareness and training. The medium severity score suggests that while the vulnerability is not critical, it should be addressed promptly to prevent escalation or chaining with other vulnerabilities.

Summary

CVE-2025-64560 is a DOM-based Cross-Site Scripting (XSS) vulnerability identified in Adobe Experience Manager (AEM) versions 6.5.23 and earlier. This vulnerability arises from improper handling of untrusted data within the Document Object Model (DOM) in the web application, allowing an attacker to inject malicious scripts that execute in the context of the victim's browser. Unlike traditional reflected or stored XSS, DOM-based XSS occurs entirely on the client side, where the malicious payload manipulates the DOM environment to execute code. The attacker, with low privileges, can craft a malicious URL or web page that, when visited or interacted with by a user, triggers the execution of arbitrary JavaScript. This can lead to unauthorized actions such as session hijacking, theft of sensitive information, or manipulation of the user interface. The vulnerability requires user interaction, which limits automated exploitation but does not eliminate risk, especially in targeted phishing or social engineering campaigns. The CVSS 3.1 base score of 5.4 reflects a medium severity level, with attack vector being network (remote), low attack complexity, low privileges required, and user interaction necessary. The scope is changed, indicating that the vulnerability affects components beyond the initially vulnerable module, potentially impacting other parts of the application. No patches or known exploits are currently available, emphasizing the importance of proactive mitigation. The vulnerability is classified under CWE-79, which covers Cross-Site Scripting issues.

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