CVE-2025-64575: Cross-site Scripting (Stored XSS) (CWE-79) in Adobe Adobe Experience Manager
Adobe Experience Manager versions 6.5.23 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.
AI Analysis
Technical Summary
CVE-2025-64575 is a stored Cross-Site Scripting (XSS) vulnerability identified in Adobe Experience Manager (AEM) versions 6.5.23 and earlier. The 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 persistently on the server. When a victim user accesses a page containing the injected script, the malicious code executes in their browser context, potentially leading to session hijacking, credential theft, or unauthorized actions performed with the victim's privileges. The vulnerability requires the attacker to have low-level privileges to submit data to the vulnerable form fields and requires user interaction to trigger the malicious script execution. The CVSS v3.1 base score of 5.4 reflects that the attack vector is network-based, with low attack complexity, requiring privileges and user interaction, and impacts confidentiality and integrity with no availability impact. The scope is changed (S:C) indicating that the vulnerability affects components beyond the vulnerable component itself, possibly impacting other parts of the system or user sessions. No patches were listed at the time of publication, and no known exploits in the wild have been reported. Given Adobe Experience Manager's widespread use in enterprise content management and web experience delivery, this vulnerability poses a moderate risk to organizations relying on AEM for public-facing or internal web portals.
Potential Impact
For European organizations, the impact of CVE-2025-64575 can be significant in scenarios where Adobe Experience Manager is used to deliver web content to employees, partners, or customers. Successful exploitation could lead to unauthorized disclosure of sensitive information such as session cookies or personal data, enabling further attacks like account takeover or lateral movement within the network. The integrity of web content could be compromised, damaging organizational reputation and trust. Although availability is not directly impacted, the indirect consequences of data leakage or unauthorized actions could disrupt business operations. Organizations in sectors with strict data protection regulations, such as finance, healthcare, and government, face heightened risks due to potential GDPR violations and associated penalties. The requirement for user interaction and low privileges lowers the barrier for exploitation, especially in environments with many users accessing AEM-managed portals. The absence of known exploits in the wild suggests a window of opportunity for proactive mitigation before widespread attacks occur.
Mitigation Recommendations
1. Monitor Adobe’s official security advisories closely and apply patches or updates as soon as they become available to address CVE-2025-64575. 2. Implement strict input validation on all form fields within Adobe Experience Manager to reject or sanitize potentially malicious input before storage. 3. Employ robust output encoding techniques to ensure that any user-supplied data rendered in web pages is properly escaped, preventing script execution. 4. Use Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing AEM content. 5. Conduct regular security audits and penetration testing focused on web application vulnerabilities, including stored XSS. 6. Educate users about the risks of clicking on suspicious links or interacting with untrusted content within corporate portals. 7. Enable logging and monitoring to detect unusual input patterns or script injection attempts in AEM logs. 8. Consider deploying Web Application Firewalls (WAFs) with rules tuned to detect and block XSS payloads targeting AEM. 9. Limit privileges for users who can submit content to only those necessary, reducing the attack surface. 10. Review and harden AEM configurations to minimize exposure of vulnerable components or forms.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain
CVE-2025-64575: Cross-site Scripting (Stored XSS) (CWE-79) in Adobe Adobe Experience Manager
Description
Adobe Experience Manager versions 6.5.23 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.
AI-Powered Analysis
Technical Analysis
CVE-2025-64575 is a stored Cross-Site Scripting (XSS) vulnerability identified in Adobe Experience Manager (AEM) versions 6.5.23 and earlier. The 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 persistently on the server. When a victim user accesses a page containing the injected script, the malicious code executes in their browser context, potentially leading to session hijacking, credential theft, or unauthorized actions performed with the victim's privileges. The vulnerability requires the attacker to have low-level privileges to submit data to the vulnerable form fields and requires user interaction to trigger the malicious script execution. The CVSS v3.1 base score of 5.4 reflects that the attack vector is network-based, with low attack complexity, requiring privileges and user interaction, and impacts confidentiality and integrity with no availability impact. The scope is changed (S:C) indicating that the vulnerability affects components beyond the vulnerable component itself, possibly impacting other parts of the system or user sessions. No patches were listed at the time of publication, and no known exploits in the wild have been reported. Given Adobe Experience Manager's widespread use in enterprise content management and web experience delivery, this vulnerability poses a moderate risk to organizations relying on AEM for public-facing or internal web portals.
Potential Impact
For European organizations, the impact of CVE-2025-64575 can be significant in scenarios where Adobe Experience Manager is used to deliver web content to employees, partners, or customers. Successful exploitation could lead to unauthorized disclosure of sensitive information such as session cookies or personal data, enabling further attacks like account takeover or lateral movement within the network. The integrity of web content could be compromised, damaging organizational reputation and trust. Although availability is not directly impacted, the indirect consequences of data leakage or unauthorized actions could disrupt business operations. Organizations in sectors with strict data protection regulations, such as finance, healthcare, and government, face heightened risks due to potential GDPR violations and associated penalties. The requirement for user interaction and low privileges lowers the barrier for exploitation, especially in environments with many users accessing AEM-managed portals. The absence of known exploits in the wild suggests a window of opportunity for proactive mitigation before widespread attacks occur.
Mitigation Recommendations
1. Monitor Adobe’s official security advisories closely and apply patches or updates as soon as they become available to address CVE-2025-64575. 2. Implement strict input validation on all form fields within Adobe Experience Manager to reject or sanitize potentially malicious input before storage. 3. Employ robust output encoding techniques to ensure that any user-supplied data rendered in web pages is properly escaped, preventing script execution. 4. Use Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing AEM content. 5. Conduct regular security audits and penetration testing focused on web application vulnerabilities, including stored XSS. 6. Educate users about the risks of clicking on suspicious links or interacting with untrusted content within corporate portals. 7. Enable logging and monitoring to detect unusual input patterns or script injection attempts in AEM logs. 8. Consider deploying Web Application Firewalls (WAFs) with rules tuned to detect and block XSS payloads targeting AEM. 9. Limit privileges for users who can submit content to only those necessary, reducing the attack surface. 10. Review and harden AEM configurations to minimize exposure of vulnerable components or forms.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- adobe
- Date Reserved
- 2025-11-05T22:51:33.028Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6939bda9fe7b3954b690b303
Added to database: 12/10/2025, 6:36:25 PM
Last enriched: 12/17/2025, 7:40:40 PM
Last updated: 2/5/2026, 6:55:21 PM
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-1707: Vulnerability in pgadmin.org pgAdmin 4
HighCVE-2025-68121: CWE-295: Improper Certificate Validation in Go standard library crypto/tls
HighCVE-2025-58190: CWE-835: Loop with Unreachable Exit Condition in golang.org/x/net golang.org/x/net/html
HighCVE-2025-47911: CWE-400: Uncontrolled Resource Consumption in golang.org/x/net golang.org/x/net/html
HighCVE-2025-15557: CWE-295 Improper Certificate Validation in TP-Link Systems Inc. Tapo H100 v1
HighActions
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.