CVE-2025-46911: Adobe Experience Manager · Cross-site Scripting (Stored XSS)
Affects Adobe Experience ManagerSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Adobe Adobe Experience Manager | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigation steps: 1) Immediately audit user privileges within AEM to ensure that only trusted personnel have high-level access capable of injecting content. 2) Apply strict input validation and output encoding on all form fields, especially those that accept user-generated content, to prevent script injection. 3) Monitor AEM logs for unusual activities or unexpected content changes that could indicate exploitation attempts. 4) Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers accessing the AEM environment. 5) Segregate administrative interfaces from public-facing components to reduce exposure. 6) Regularly update and patch AEM once Adobe releases an official fix for this vulnerability. 7) Conduct security awareness training for administrators to recognize social engineering or phishing attempts that could lead to privilege escalation. 8) Employ web application firewalls (WAFs) with rules tuned to detect and block XSS payloads targeting AEM. These measures go beyond generic advice by focusing on privilege management, monitoring, and layered defenses tailored to the AEM context.
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 high 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.