CVE-2025-64611: Cross-site Scripting (Stored XSS) (CWE-79) in Adobe Adobe Experience Manager
CVE-2025-64611 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 browser of users who visit the affected pages. This vulnerability requires user interaction and some privileges but can lead to partial compromise of confidentiality and integrity. The CVSS score is 5. 4 (medium severity), reflecting network attack vector, low attack complexity, and requirement for user interaction. No known exploits are currently reported in the wild. European organizations using AEM for content management and digital experience delivery should prioritize patching or mitigating this vulnerability to prevent potential data theft, session hijacking, or defacement. Countries with high adoption of Adobe Experience Manager, such as Germany, France, and the UK, are most likely to be affected.
AI Analysis
Technical Summary
CVE-2025-64611 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 in 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 other users access the affected pages, the malicious script executes in their browsers, potentially allowing attackers 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. The attack vector is network-based (AV:N), with low attack complexity (AC:L), requiring low privileges (PR:L) and user interaction (UI:R). The scope is changed (S:C), meaning the vulnerability affects resources beyond the initially vulnerable component. The impact affects confidentiality and integrity partially (C:L, I:L) but not availability (A:N). No public exploits are known at this time, but the vulnerability poses a risk due to the widespread use of AEM in enterprise content management. The lack of available patches at the time of reporting necessitates immediate mitigation efforts to prevent exploitation.
Potential Impact
For European organizations, the impact of this vulnerability can be significant, especially for those relying on Adobe Experience Manager for managing digital content and customer experiences. Exploitation could lead to unauthorized disclosure of sensitive information, such as session tokens or personal data, compromising user confidentiality. Attackers could also manipulate content integrity by injecting malicious scripts that alter displayed information or perform unauthorized actions on behalf of users. While availability is not directly impacted, the reputational damage and potential regulatory penalties under GDPR for data breaches could be severe. Organizations in sectors like finance, healthcare, government, and e-commerce, which often use AEM for their web platforms, are particularly at risk. The requirement for user interaction and low privileges lowers the barrier for exploitation, increasing the likelihood of targeted attacks or phishing campaigns leveraging this vulnerability.
Mitigation Recommendations
To mitigate CVE-2025-64611, organizations should first monitor Adobe's official channels for patches and apply them promptly once available. In the interim, implement strict input validation and output encoding on all form fields within AEM to prevent malicious script injection. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS payloads. Conduct regular security audits and penetration testing focused on web application vulnerabilities, including XSS. Educate users and administrators about the risks of interacting with suspicious content and ensure that least privilege principles are enforced for user accounts within AEM. Additionally, consider deploying Web Application Firewalls (WAFs) with rules tailored to detect and block XSS attack patterns targeting AEM. Logging and monitoring should be enhanced to detect anomalous activities indicative of exploitation attempts.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Sweden
CVE-2025-64611: Cross-site Scripting (Stored XSS) (CWE-79) in Adobe Adobe Experience Manager
Description
CVE-2025-64611 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 browser of users who visit the affected pages. This vulnerability requires user interaction and some privileges but can lead to partial compromise of confidentiality and integrity. The CVSS score is 5. 4 (medium severity), reflecting network attack vector, low attack complexity, and requirement for user interaction. No known exploits are currently reported in the wild. European organizations using AEM for content management and digital experience delivery should prioritize patching or mitigating this vulnerability to prevent potential data theft, session hijacking, or defacement. Countries with high adoption of Adobe Experience Manager, such as Germany, France, and the UK, are most likely to be affected.
AI-Powered Analysis
Technical Analysis
CVE-2025-64611 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 in 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 other users access the affected pages, the malicious script executes in their browsers, potentially allowing attackers 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. The attack vector is network-based (AV:N), with low attack complexity (AC:L), requiring low privileges (PR:L) and user interaction (UI:R). The scope is changed (S:C), meaning the vulnerability affects resources beyond the initially vulnerable component. The impact affects confidentiality and integrity partially (C:L, I:L) but not availability (A:N). No public exploits are known at this time, but the vulnerability poses a risk due to the widespread use of AEM in enterprise content management. The lack of available patches at the time of reporting necessitates immediate mitigation efforts to prevent exploitation.
Potential Impact
For European organizations, the impact of this vulnerability can be significant, especially for those relying on Adobe Experience Manager for managing digital content and customer experiences. Exploitation could lead to unauthorized disclosure of sensitive information, such as session tokens or personal data, compromising user confidentiality. Attackers could also manipulate content integrity by injecting malicious scripts that alter displayed information or perform unauthorized actions on behalf of users. While availability is not directly impacted, the reputational damage and potential regulatory penalties under GDPR for data breaches could be severe. Organizations in sectors like finance, healthcare, government, and e-commerce, which often use AEM for their web platforms, are particularly at risk. The requirement for user interaction and low privileges lowers the barrier for exploitation, increasing the likelihood of targeted attacks or phishing campaigns leveraging this vulnerability.
Mitigation Recommendations
To mitigate CVE-2025-64611, organizations should first monitor Adobe's official channels for patches and apply them promptly once available. In the interim, implement strict input validation and output encoding on all form fields within AEM to prevent malicious script injection. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of potential XSS payloads. Conduct regular security audits and penetration testing focused on web application vulnerabilities, including XSS. Educate users and administrators about the risks of interacting with suspicious content and ensure that least privilege principles are enforced for user accounts within AEM. Additionally, consider deploying Web Application Firewalls (WAFs) with rules tailored to detect and block XSS attack patterns targeting AEM. Logging and monitoring should be enhanced to detect anomalous activities indicative of exploitation attempts.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- adobe
- Date Reserved
- 2025-11-05T22:53:10.942Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6939bdaefe7b3954b690bb7f
Added to database: 12/10/2025, 6:36:30 PM
Last enriched: 12/17/2025, 9:01:13 PM
Last updated: 2/4/2026, 4:08:34 AM
Views: 25
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-1791: CWE-434 Unrestricted Upload of File with Dangerous Type in Hillstone Networks Operation and Maintenance Security Gateway
LowCVE-2026-1835: Cross-Site Request Forgery in lcg0124 BootDo
MediumCVE-2026-1813: Unrestricted Upload in bolo-blog bolo-solo
MediumCVE-2026-1632: CWE-306 Missing Authentication for Critical Function in RISS SRL MOMA Seismic Station
CriticalCVE-2026-1812: Path Traversal in bolo-blog bolo-solo
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.