CVE-2025-64572VulnerabilityPublished 10 Dec 2025

CVE-2025-64572: Adobe Experience Manager · Cross-site Scripting (Stored XSS)

Affects Adobe Experience ManagerSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 25 Oct 2026, 19:02 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-25.

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 official Adobe patches or updates as soon as they become available to address CVE-2025-64572. 2. Until patches are released, implement strict input validation and output encoding on all user-supplied data in AEM forms to prevent script injection. 3. Deploy Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks. 4. Conduct regular security audits and code reviews focusing on input handling in AEM components. 5. Monitor web server and application logs for unusual activity or script injection attempts. 6. Educate developers and administrators on secure coding practices related to XSS vulnerabilities. 7. Consider using Web Application Firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting AEM. 8. Limit user privileges where possible to reduce the attack surface and potential for malicious input submission. 9. Implement multi-factor authentication (MFA) to protect user accounts that could be targeted via session hijacking. 10. Maintain an incident response plan to quickly address any detected exploitation attempts.

Description

CVE-2025-64572 is a stored Cross-Site Scripting (XSS) vulnerability affecting Adobe Experience Manager (AEM) versions 6.5.23 and earlier. A low-privileged attacker can inject malicious JavaScript into vulnerable form fields, which executes in the browsers of users who visit the affected pages. This vulnerability requires user interaction and some privileges but can lead to confidentiality and integrity impacts by stealing session tokens or manipulating content. The CVSS score is 5.4 (medium severity), reflecting the moderate risk due to the need for user interaction and privileges. No known exploits are currently reported in the wild. European organizations using AEM for content management and digital experience delivery are at risk, especially those in countries with high adoption of Adobe products. Mitigation involves applying patches when available, implementing strict input validation and output encoding, and employing Content Security Policy (CSP) headers to reduce script execution risks.

Impact

For European organizations, the impact of CVE-2025-64572 can be significant, particularly for those relying on Adobe Experience Manager as a core component of their digital content management and customer engagement platforms. Exploitation could lead to unauthorized access to sensitive information such as session tokens, personal data, or internal communications, potentially violating GDPR and other data protection regulations. The integrity of web content could be compromised, misleading users or damaging brand reputation. Although availability is not directly impacted, the indirect effects of data breaches or defacement could disrupt business operations. Sectors such as finance, government, healthcare, and large enterprises with public-facing AEM deployments are particularly at risk. The medium severity rating suggests that while the vulnerability is not critical, it should be addressed promptly to prevent escalation or combined attacks. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as attackers often develop exploits after public disclosure.

Summary

CVE-2025-64572 is a stored Cross-Site Scripting (XSS) vulnerability identified in Adobe Experience Manager (AEM) versions 6.5.23 and earlier. This vulnerability arises from insufficient sanitization of user input in certain form fields, allowing a low-privileged attacker to inject malicious JavaScript code that is stored on the server and later executed in the browsers of users who access the affected pages. The attack vector is network-based, requiring the attacker to have some level of privileges (PR:L) and user interaction (UI:R) to trigger the malicious script execution. The vulnerability impacts confidentiality and integrity by enabling theft of session cookies, credentials, or manipulation of displayed content, but does not affect availability. The CVSS 3.1 base score is 5.4, indicating medium severity, with the scope changed (S:C) meaning the vulnerability can affect resources beyond the initially vulnerable component. No public exploits or active exploitation in the wild have been reported to date. Adobe has not yet released patches, but organizations are advised to monitor for updates. The vulnerability is classified under CWE-79, a common and well-understood XSS weakness. Given AEM’s role in managing digital content and user interactions, exploitation could lead to significant reputational damage and data leakage if attackers successfully execute malicious scripts within trusted web applications.

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, 21:03 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats