Skip to main content

CVE-2025-47005: Cross-site Scripting (DOM-based XSS) (CWE-79) in Adobe Adobe Experience Manager

Medium
VulnerabilityCVE-2025-47005cvecve-2025-47005cwe-79
Published: Tue Jun 10 2025 (06/10/2025, 22:19:07 UTC)
Source: CVE Database V5
Vendor/Project: Adobe
Product: Adobe Experience Manager

Description

Adobe Experience Manager versions 6.5.22 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: 07/11/2025, 11:03:34 UTC

Technical Analysis

CVE-2025-47005 is a stored Cross-Site Scripting (XSS) vulnerability affecting Adobe Experience Manager (AEM) versions 6.5.22 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 on the server. When a victim accesses the affected page containing the vulnerable form field, the malicious script executes in their browser context. This is a DOM-based XSS, meaning the attack payload manipulates the Document Object Model on the client side, potentially bypassing some traditional input validation mechanisms. The vulnerability requires attacker privileges to submit malicious input and user interaction to trigger script execution. The CVSS v3.1 base score is 5.4 (medium severity), reflecting network attack vector, low attack complexity, low privileges required, and requirement for user interaction. The impact includes limited confidentiality and integrity compromise, as the attacker can execute scripts in the victim’s browser, potentially stealing session tokens, performing actions on behalf of the user, or defacing content. Availability is not impacted. No known exploits are currently reported in the wild, and no official patches have been linked yet. The vulnerability is classified under CWE-79 (Improper Neutralization of Input During Web Page Generation), a common and well-understood web security issue. Given AEM’s role as a content management system widely used by enterprises for web content delivery, exploitation could lead to significant reputational damage and data leakage if sensitive user sessions are compromised.

Potential Impact

For European organizations, the impact of this vulnerability can be significant, particularly for those relying on Adobe Experience Manager for public-facing websites or intranet portals. Successful exploitation could allow attackers to hijack user sessions, steal credentials, or perform unauthorized actions within the context of the victim’s browser session. This can lead to data breaches, unauthorized access to sensitive information, and erosion of user trust. Industries such as finance, government, healthcare, and e-commerce, which often use AEM for their digital presence, are at higher risk due to the sensitivity of the data involved. Additionally, regulatory frameworks like GDPR impose strict requirements on protecting personal data, and exploitation of this vulnerability could result in compliance violations and financial penalties. The medium severity score indicates that while the vulnerability is not critical, it still poses a tangible risk that must be addressed promptly to prevent potential exploitation, especially in environments with high user interaction and public accessibility.

Mitigation Recommendations

To mitigate this vulnerability effectively, organizations should: 1) Immediately review and restrict user input fields in AEM to ensure proper input validation and output encoding, particularly focusing on form fields that accept user-generated content. 2) Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. 3) Monitor web application logs for unusual input patterns or repeated attempts to inject scripts. 4) Educate developers and administrators on secure coding practices specific to DOM-based XSS, emphasizing the importance of sanitizing data both on client and server sides. 5) Apply any available patches or updates from Adobe as soon as they are released. 6) Consider deploying Web Application Firewalls (WAFs) with rules tailored to detect and block XSS payloads targeting AEM. 7) Conduct regular security assessments and penetration testing focused on web application vulnerabilities to identify and remediate similar issues proactively.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
adobe
Date Reserved
2025-04-30T20:47:54.992Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6848b1993cd93dcca8311faf

Added to database: 6/10/2025, 10:28:41 PM

Last enriched: 7/11/2025, 11:03:34 AM

Last updated: 8/6/2025, 12:19:31 AM

Views: 24

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

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