CVE-2025-64820VulnerabilityPublished 10 Dec 2025

CVE-2025-64820: 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 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. Monitor Adobe’s official channels for patches and apply them promptly once released. 2. Until a patch is available, implement strict input validation and output encoding on all form fields within AEM to prevent malicious script injection. 3. Deploy Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 4. Limit user privileges on AEM to reduce the ability of low-privileged users to inject malicious content. 5. Conduct regular security audits and penetration testing focusing on web application vulnerabilities, including XSS. 6. Educate users about phishing risks and suspicious links to reduce the likelihood of triggering malicious scripts. 7. Use web application firewalls (WAFs) with rules designed to detect and block XSS payloads targeting AEM. 8. Review and sanitize any existing stored data in vulnerable form fields to remove malicious scripts. 9. Implement multi-factor authentication to reduce the impact of session hijacking if exploitation occurs.

Description

CVE-2025-64820 is a stored Cross-Site Scripting (XSS) vulnerability affecting Adobe Experience Manager (AEM) versions 6.5.23 and earlier. This vulnerability allows a low-privileged attacker to inject malicious JavaScript into vulnerable form fields, which executes in the browser of any user viewing the affected page. The vulnerability requires user interaction to trigger and has a medium CVSS score of 5.4. While no known exploits are currently reported in the wild, the vulnerability poses risks to confidentiality and integrity by enabling script injection and potential session hijacking or data theft. European organizations using AEM for content management and digital experience delivery should prioritize patching or mitigating this issue. Countries with significant digital service sectors and high AEM adoption, such as Germany, France, and the UK, are particularly at risk. Mitigation includes applying patches when available, implementing strict input validation and output encoding, and employing Content Security Policy (CSP) headers to limit script execution.

Impact

For European organizations, the impact of this vulnerability can be substantial, especially for those relying on Adobe Experience Manager to deliver web content and digital experiences. Successful exploitation could lead to unauthorized access to sensitive user data, session hijacking, and potential defacement or redirection of websites. This undermines user trust and can lead to regulatory repercussions under GDPR if personal data is compromised. The medium severity score reflects moderate risk, but the widespread adoption of AEM in sectors such as finance, government, and e-commerce across Europe amplifies the potential damage. Attackers exploiting this vulnerability could target employees or customers, leading to credential theft or further network infiltration. Additionally, the stored nature of the XSS means the malicious payload persists, increasing exposure duration. The requirement for user interaction limits automated exploitation but does not eliminate risk, especially in phishing or social engineering scenarios.

Summary

CVE-2025-64820 is a stored Cross-Site Scripting (XSS) vulnerability identified in Adobe Experience Manager (AEM) versions 6.5.23 and earlier. Stored XSS occurs when malicious input is permanently stored on the target server, such as within form fields, and later rendered in users' browsers without proper sanitization or encoding. In this case, a low-privileged attacker can inject arbitrary JavaScript code into vulnerable form fields within AEM. When legitimate users access pages containing these fields, the malicious script executes in their browsers, potentially allowing the attacker to steal session cookies, perform actions on behalf of the user, or redirect users to malicious sites. The vulnerability has a CVSS 3.1 base score of 5.4, indicating medium severity, with an attack vector of network, low attack complexity, requiring privileges, and user interaction. The scope is changed, meaning the vulnerability affects components beyond the initially vulnerable part. No public exploits are known yet, but the risk remains significant due to AEM's widespread use in enterprise content management. The vulnerability impacts confidentiality and integrity but not availability. Adobe has not yet released a patch, so organizations must rely on interim mitigations.

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:58 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats