CVE-2025-53693: Sitecore Experience Manager (XM) · Unsafe Reflection
Affects Sitecore Experience Manager (XM)Source CVE Database V5
Not known to be exploited · 19% EPSS · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 19.9% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Sep 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 |
|---|---|---|
| Sitecore Sitecore Experience Manager (XM) | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability effectively, European organizations should: 1) Immediately identify and inventory all Sitecore XM and XP instances within their environment, focusing on versions 9.0 through 9.3 and 10.0 through 10.4. 2) Apply vendor-provided patches or updates as soon as they become available; if no patches are currently released, engage with Sitecore support for recommended interim mitigations. 3) Implement strict input validation and sanitization controls at the application layer to prevent unsafe reflection by disallowing or tightly controlling any user-controllable inputs that influence class or code loading. 4) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests that attempt to exploit unsafe reflection patterns or cache poisoning behaviors. 5) Monitor application and system logs for unusual cache modifications, unexpected class loading activities, or anomalous network traffic indicative of exploitation attempts. 6) Restrict network exposure of Sitecore management interfaces and ensure they are accessible only from trusted networks or via VPN. 7) Conduct security awareness and training for development and operations teams on the risks of unsafe reflection and secure coding practices. 8) Consider deploying runtime application self-protection (RASP) technologies that can detect and block reflective code injection attempts in real time.
Description
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Sitecore Sitecore Experience Manager (XM), Sitecore Experience Platform (XP) allows Cache Poisoning.This issue affects Sitecore Experience Manager (XM): from 9.0 through 9.3, from 10.0 through 10.4; Experience Platform (XP): from 9.0 through 9.3, from 10.0 through 10.4.