CVE-2025-46943: 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, 09:15 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% 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 immediately audit their Adobe Experience Manager deployments to identify affected versions (6.5.22 and earlier). Until an official patch is released, organizations should implement strict input validation and output encoding on all form fields to neutralize potentially malicious scripts. Employing Web Application Firewalls (WAFs) with custom rules to detect and block XSS payloads targeting AEM can provide a temporary defense layer. Additionally, organizations should review user privilege assignments to minimize the number of users with permissions to submit or modify content in vulnerable fields. Security teams should monitor web traffic and logs for unusual activity indicative of attempted XSS exploitation. Educating users about the risks of clicking suspicious links and encouraging the use of modern browsers with built-in XSS protections can reduce the likelihood of successful attacks. Once Adobe releases a patch, organizations must prioritize timely deployment and validate the fix in their environments. Finally, adopting Content Security Policy (CSP) headers can help mitigate the impact of injected scripts by restricting script execution sources.
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.