Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-64585: Cross-site Scripting (Stored XSS) (CWE-79) in Adobe Adobe Experience Manager

0
Medium
VulnerabilityCVE-2025-64585cvecve-2025-64585cwe-79
Published: Wed Dec 10 2025 (12/10/2025, 18:23:03 UTC)
Source: CVE Database V5
Vendor/Project: Adobe
Product: 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

AILast updated: 12/10/2025, 19:15:08 UTC

Technical Analysis

CVE-2025-64585 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 persistently on the server. When legitimate users access the affected pages containing these vulnerable fields, the malicious script executes in their browsers within the security context of the AEM application. The attack vector is network-based with low attack complexity and requires low privileges but does require user interaction (visiting the compromised page). 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. No public exploits or active exploitation have been reported yet, but the risk remains significant due to the widespread use of AEM in enterprise content management. The vulnerability is classified under CWE-79, a common and well-understood web security issue. Technical mitigation involves sanitizing inputs, applying strict Content Security Policies (CSP), and restricting access to vulnerable form fields. Adobe has not yet released a patch as of the published date, so organizations must implement compensating controls to reduce risk.

Potential Impact

For European organizations, the impact of this vulnerability can be substantial, especially for those relying heavily on Adobe Experience Manager for web content and digital experience delivery. Successful exploitation could lead to unauthorized disclosure of sensitive information such as session tokens, user credentials, or personal data, violating GDPR and other data protection regulations. Integrity of web content could be compromised, potentially damaging brand reputation and user trust. Although availability is not directly impacted, the indirect effects of data breaches or defacement could disrupt business operations. Given the medium CVSS score and the requirement for user interaction, the threat is moderate but should not be underestimated. Organizations in sectors such as finance, government, healthcare, and e-commerce, which often use AEM and handle sensitive data, are particularly at risk. Additionally, the persistent nature of stored XSS means that once injected, malicious scripts can affect multiple users over time, increasing the potential damage.

Mitigation Recommendations

1. Apply input validation and output encoding rigorously on all form fields to prevent injection of malicious scripts. 2. Implement and enforce strict Content Security Policies (CSP) to restrict the execution of unauthorized scripts. 3. Limit access to vulnerable form fields by applying role-based access controls and minimizing privileges for users who can submit data. 4. Monitor web application logs and user activity for unusual behavior indicative of XSS exploitation attempts. 5. Educate developers and content managers about secure coding practices and the risks of XSS vulnerabilities. 6. Regularly update Adobe Experience Manager to the latest versions once patches are released by Adobe. 7. Use web application firewalls (WAF) with rules specifically designed to detect and block XSS payloads targeting AEM. 8. Conduct periodic security assessments and penetration testing focused on input handling and client-side script execution.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
adobe
Date Reserved
2025-11-05T22:53:10.939Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6939bdaafe7b3954b690b328

Added to database: 12/10/2025, 6:36:26 PM

Last enriched: 12/10/2025, 7:15:08 PM

Last updated: 12/11/2025, 4:55:18 AM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats