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

0
Medium
VulnerabilityCVE-2025-47061cvecve-2025-47061cwe-79
Published: Thu Jul 24 2025 (07/24/2025, 15:22:40 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/24/2025, 16:02:56 UTC

Technical Analysis

CVE-2025-47061 is a stored Cross-Site Scripting (XSS) vulnerability affecting Adobe Experience Manager (AEM) versions 6.5.22 and earlier. This vulnerability arises from insufficient input sanitization in certain form fields within the AEM platform, allowing a low-privileged attacker to inject malicious JavaScript code that is persistently stored on the server. When a victim user accesses a page containing the compromised form field, the malicious script executes in their browser context. The vulnerability is classified under CWE-79, indicating improper neutralization of input during web page generation. The CVSS v3.1 base score is 5.4 (medium severity), with vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, meaning the attack can be launched remotely over the network with low attack complexity, requires low privileges, and user interaction is necessary. The scope is changed (S:C), indicating that the vulnerability affects resources beyond the initially vulnerable component. The impact affects confidentiality and integrity to a limited extent, with no direct availability impact. No known exploits are currently reported in the wild, and no official patches have been linked yet. Stored XSS in AEM is particularly dangerous because AEM is widely used for enterprise content management and digital experience delivery, often hosting public-facing websites and intranet portals. Successful exploitation could lead to session hijacking, credential theft, defacement, or distribution of malware to users of the affected sites.

Potential Impact

For European organizations, the impact of this vulnerability can be significant due to the widespread adoption of Adobe Experience Manager in government, finance, healthcare, and large enterprises across Europe. Exploitation could lead to unauthorized access to sensitive user data, compromise of user sessions, and erosion of trust in digital services. Since AEM often serves as the backbone for customer-facing portals and internal collaboration platforms, attackers could leverage this vulnerability to conduct targeted phishing campaigns, steal credentials, or pivot to further internal network compromise. The medium severity score reflects the need for user interaction and low privilege requirements, but the potential for scope change and persistent script injection raises concerns for data confidentiality and integrity. Additionally, compliance with GDPR and other European data protection regulations means that exploitation resulting in data leakage could lead to regulatory penalties and reputational damage.

Mitigation Recommendations

European organizations using Adobe Experience Manager should implement the following specific mitigations: 1) Immediately review and restrict user permissions to minimize low-privileged users' ability to submit content to vulnerable form fields. 2) Employ rigorous input validation and output encoding on all user-supplied data, particularly in form fields exposed on public or internal web pages. 3) Monitor web application logs and user activity for unusual or suspicious input patterns indicative of XSS attempts. 4) Deploy Web Application Firewalls (WAFs) with custom rules targeting known XSS payloads and patterns specific to AEM form submissions. 5) Conduct thorough security testing, including automated and manual penetration tests focusing on stored XSS vectors within AEM environments. 6) Stay alert for Adobe's official patches or security advisories and apply updates promptly once available. 7) Educate users and administrators about the risks of XSS and safe browsing practices to reduce the likelihood of successful exploitation. 8) Consider implementing Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts on affected web pages.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 688255a1ad5a09ad003a1ecc

Added to database: 7/24/2025, 3:47:45 PM

Last enriched: 7/24/2025, 4:02:56 PM

Last updated: 10/30/2025, 2:12:52 PM

Views: 63

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