CVE-2025-53693
Sitecore Experience Platform 9.0 – 10.4
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-53693 is a critical-severity Unsafe Reflection (CWE-470) vulnerability in Sitecore Experience Platform. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Reflective Code Loading (T1620); ranked in the top 4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-53693 is a Use of Externally-Controlled Input to Select Classes or Code vulnerability, known as 'Unsafe Reflection' and mapped to CWE-470, present in Sitecore Experience Manager (XM) versions from 9.0 through 9.3 and 10.0 through 10.4, as well as Sitecore Experience Platform (XP) versions from 9.0 through 9.3 and 10.0 through 10.4. This flaw allows for cache poisoning by leveraging externally controlled input to influence class or code selection.
With a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), the vulnerability is exploitable over the network by unauthenticated attackers requiring low complexity and no user interaction. Successful exploitation enables high-impact disruption to confidentiality, integrity, and availability, facilitating cache poisoning that can escalate to remote code execution.
Advisories from Watchtower Labs (https://labs.watchtowr.com/cache-me-if-you-can-sitecore-experience-platform-cache-poisoning-to-rce/) and Sitecore's knowledge base (https://support.sitecore.com/kb?id=kb_article_view&sysparm_article=KB1003667) provide details on mitigation, including patches and configuration guidance for affected Sitecore XM and XP deployments.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-26500
Vulnerability Data
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…
more
Platform (XP): from 9.0 through 9.3, from 10.0 through 10.4.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly stops externally supplied class or method names from selecting improper code via reflection.
Enforces authorization checks on the code or classes ultimately invoked, blocking unauthorized selections even if reflection is used.
Limits privileges of any code reached through unsafe reflection, reducing blast radius without stopping the selection itself.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly avoid introducing externally controlled class selection via reflection.
Vulnerability identification processes can discover unsafe reflection during code review or scanning.
Preventing execution of unauthorized code can block exploitation of unsafe reflection at runtime.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards directly forbid unsafe reflection and require whitelisting or static alternatives.
Security testing can detect and block unsafe reflection patterns before release.
Secure development lifecycle mandates input validation and design reviews that reduce unsafe reflection risks.
Application security requirements can explicitly prohibit or constrain reflection based on untrusted input.
Secure architecture principles discourage dynamic class loading from external data sources.
Access restrictions limit who can supply the malicious input but do not address the reflection flaw itself.