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-64622: Cross-site Scripting (Stored XSS) (CWE-79) in Adobe Adobe Experience Manager

0
Medium
VulnerabilityCVE-2025-64622cvecve-2025-64622cwe-79
Published: Wed Dec 10 2025 (12/10/2025, 18:24:27 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:22:50 UTC

Technical Analysis

CVE-2025-64622 is a stored Cross-Site Scripting (XSS) vulnerability identified in Adobe Experience Manager (AEM), specifically affecting versions 6.5.23 and earlier. This vulnerability arises from insufficient sanitization of user-supplied input in form fields, allowing a low-privileged attacker to inject malicious JavaScript code that is persistently stored on the server. When a victim user accesses the compromised page, the injected script executes within their browser context, potentially leading to session hijacking, credential theft, or unauthorized actions performed with the victim's privileges. The vulnerability is classified under CWE-79, indicating a classic XSS flaw. The CVSS v3.1 base score is 5.4, reflecting a medium severity level, with the vector indicating network attack vector (AV:N), 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. Confidentiality and integrity impacts are rated low, with no impact on availability. No public exploits have been reported yet, but the presence of stored XSS in a widely used enterprise content management system poses a significant risk, especially in environments where multiple users access the platform. The vulnerability was reserved in early November 2025 and published in December 2025, with no patch links currently available, indicating that remediation may still be pending or in progress.

Potential Impact

For European organizations, the impact of CVE-2025-64622 can be significant, especially for those relying on Adobe Experience Manager for managing web content and digital assets. Successful exploitation can lead to unauthorized access to user sessions, theft of sensitive information, and potential compromise of internal systems if attackers leverage the XSS to perform further attacks such as privilege escalation or lateral movement. The vulnerability's ability to affect multiple users through stored payloads increases the risk of widespread compromise within an organization. Confidentiality and integrity of user data and organizational information are at risk, which can lead to reputational damage, regulatory penalties under GDPR, and operational disruptions. The requirement for user interaction and low privileges lowers the barrier for exploitation, making it a feasible attack vector for threat actors targeting European enterprises. Additionally, organizations in sectors such as finance, government, and media, which often use AEM for public-facing and internal portals, may face heightened risks.

Mitigation Recommendations

To mitigate CVE-2025-64622, European organizations should implement a multi-layered approach: 1) Apply patches from Adobe immediately once available to address the root cause of the vulnerability. 2) In the interim, enforce strict input validation and sanitization on all form fields within AEM to prevent malicious script injection. 3) Implement robust output encoding/escaping mechanisms to ensure that any user-supplied data rendered on web pages does not execute as code. 4) Restrict user privileges, limiting the ability to submit or modify content to trusted users only. 5) Employ Content Security Policy (CSP) headers to reduce the impact of potential XSS by restricting the sources from which scripts can be loaded. 6) Monitor web application logs and user activity for signs of suspicious behavior or injection attempts. 7) Conduct regular security assessments and penetration testing focused on web application vulnerabilities. 8) Educate users about the risks of interacting with untrusted content and encourage reporting of unusual behavior. These steps collectively reduce the risk and impact of exploitation until a permanent fix is deployed.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 6939bdaefe7b3954b690bb9a

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

Last enriched: 12/10/2025, 7:22:50 PM

Last updated: 12/11/2025, 3:47:26 AM

Views: 6

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