CVE Alert: CVE-2025-53690 – Sitecore – Experience Manager (XM)

CVE-2025-53690

CRITICALNo exploitation known

Deserialization of Untrusted Data vulnerability in Sitecore Experience Manager (XM), Sitecore Experience Platform (XP) allows Code Injection.This issue affects Experience Manager (XM): through 9.0; Experience Platform (XP): through 9.0.

CVSS v3.1 (9)
AV NETWORK · AC HIGH · PR NONE · UI NONE · S CHANGED
Vendor
Sitecore, Sitecore
Product
Experience Manager (XM), Experience Platform (XP)
Versions
0 lte 9.0 | 0 lte 9.0
CWE
CWE-502, CWE-502 Deserialization of Untrusted Data
Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Published
2025-09-03T20:04:48.223Z
Updated
2025-09-04T03:55:53.472Z

AI Summary Analysis

Risk verdict

Critical risk pending exploitation signals: remote code execution is possible over the network with high impact, but current exploitation activity is not observed. If KEV is present or the EPSS score ≥ 0.5, treat as priority 1.

Why this matters

Deserialization of untrusted data enabling code injection can lead to full system compromise, data exposure, and service disruption. In environments that are exposed to the internet or integrated with authentication services, attacker goals include persistent access, data exfiltration, and lateral movement to connected systems.

Most likely attack path

An attacker could exploit over the network without user interaction and without privileges, making initial access straightforward in vulnerable deployments. Pre-conditions include running older major versions and using default or sample configuration keys. Successful exploitation yields total technical impact and can alter or compromise adjacent components due to the changed scope.

Who is most exposed

Organisations with older releases and default sample keys in production or development environments, especially those with AD integration and internet-facing endpoints, are at highest risk.

Detection ideas

  • Look for deserialization errors or unusual exceptions in web/application logs.
  • Detect anomalous payloads targeting deserialization endpoints.
  • Unusual process spawning or code execution indicators after specific requests.
  • Increased network traffic to affected endpoints from uncommon sources.
  • Key material exposure or reuse indicators in configuration files.

Mitigation and prioritisation

  • Apply the vendor-provided patch or upgrade to supported versions immediately.
  • Rotate and harden keys (replace sample keys with unique, securely stored material).
  • Restrict/monitor access to affected endpoints; implement WAF rules to block suspicious payloads.
  • Validate and harden input handling; remove any default configuration artefacts.
  • If KEV is present or EPSS ≥ 0.5, treat as priority 1; coordinate change management and test in staging before production rollout.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.