CVE-2025-46846: Adobe Experience Manager · Cross-site Scripting
Affects Adobe Experience ManagerSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Adobe Adobe Experience Manager | Affected
| Fixed in– |
AI-suggested
European organizations should prioritize the following mitigation steps: 1) Immediately review and restrict user input on all form fields within Adobe Experience Manager to ensure proper input validation and output encoding, especially for HTML and JavaScript contexts. 2) Apply any available security updates or patches from Adobe as soon as they are released. In the absence of patches, implement Web Application Firewall (WAF) rules to detect and block malicious payloads targeting AEM form fields. 3) Conduct thorough security audits and penetration testing focused on XSS vulnerabilities in AEM deployments. 4) Educate content managers and administrators about the risks of injecting untrusted content and enforce strict content security policies (CSP) to limit script execution. 5) Monitor web traffic and logs for unusual activity indicative of XSS exploitation attempts. 6) Segment AEM environments and limit administrative access to reduce the risk of low-privileged attackers injecting malicious content. 7) Consider deploying runtime application self-protection (RASP) solutions to detect and block XSS attacks in real time.
Description
Adobe Experience Manager versions 6.5.22 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low privileged attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.