CVE-2025-47049: Adobe Experience Manager · Cross-site Scripting (DOM-based XSS)
Affects Adobe Experience ManagerSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Adobe Adobe Experience Manager | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability, European organizations should prioritize the following actions: 1) Monitor Adobe's official security advisories for patches or updates addressing CVE-2025-47049 and apply them promptly once available. 2) Implement Content Security Policy (CSP) headers with strict script-src directives to limit the execution of unauthorized scripts and reduce the impact of DOM-based XSS. 3) Conduct a thorough review and hardening of client-side code in AEM customizations to ensure proper sanitization and validation of all user-controllable inputs and DOM manipulations. 4) Employ web application firewalls (WAFs) with rules designed to detect and block suspicious DOM-based XSS payloads. 5) Educate users and employees about the risks of clicking on untrusted links or visiting suspicious web pages to reduce the likelihood of successful social engineering attacks. 6) Utilize browser security features such as SameSite cookies and HttpOnly flags to protect session tokens from theft via XSS. 7) Perform regular security testing, including automated scanning and manual penetration testing focused on client-side vulnerabilities within AEM environments. These targeted measures go beyond generic advice by focusing on client-side code hygiene, user awareness, and layered defenses specific to DOM-based XSS in AEM.
Description
Adobe Experience Manager versions 6.5.22 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability. An attacker could exploit this issue by manipulating the DOM environment to execute malicious JavaScript within the context of the victim's browser. Exploitation of this issue requires user interaction in that a victim must visit a specially crafted web page.