dbcve.org
Experience CommerceApplication · Sitecore

CVE-2025-53693

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-03
Fix available
A fix is available. Upgrade to 10.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Sitecore XM and XP contain an Unsafe Reflection vulnerability where externally-controlled input is used to select classes or code for execution, allowing attackers to manipulate reflection APIs. This can lead to arbitrary code execution and cache poisoning, where malicious content is cached and served to other users.

MitigationApply vendor-provided patches for affected Sitecore versions. As an interim measure, review and restrict input handling for reflection-based operations in the application configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Experience CommerceApplication
Affected:>= 9.0, <= 10.4
Experience ManagerApplication
Affected:>= 9.0, <= 10.4
Experience PlatformApplication
Affected:>= 9.0, < 10.4= 10.4
Managed CloudApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Sitecore product and version
    Locate the Sitecore installation directory and find the version information. Typically found in the web.config file (under <appSettings> with key 'SitecoreVersion') or in the /sitecore/admin/showconfig.aspx page. Alternatively, check the DLL version of Sitecore.Kernel.dll in the bin folder.
    Affected if The product is Sitecore Experience Commerce, Experience Manager, Experience Platform, or Managed Cloud with version >= 9.0 and <= 10.4 (or < 10.4 for Experience Platform)
  2. Verify the application uses reflection-based operations
    Search the deployed application codebase for usage of System.Reflection APIs, particularly methods like Type.GetType(), Assembly.Load(), Activator.CreateInstance(), or MethodInfo.Invoke() where user-supplied input could influence the type or method name being invoked.
    Affected if Reflection APIs are used and accept external (query string, form, cookie, header) input without validation
  3. Inspect configuration for reflection settings
    Examine the web.config and sitecore.config files for any custom configuration sections that enable or control reflection-based operations. Look for settings related to 'reflection', 'type resolution', or dynamic type loading.
    Affected if Reflection-related configuration allows unrestricted type or assembly loading from external input
  4. Check for cache configuration exposure
    Review the Sitecore caching configuration in sitecore.config and any custom caching providers. Look for cache key generation that incorporates user-controlled input without sanitization.
    Affected if Cache keys or cache population logic accepts unsanitized external input
  5. Audit HTTP request handling for reflection endpoints
    Review the sitecore and sitecore/api routes in the application. Examine any custom pipelines or controllers that handle incoming requests and pass them to reflection APIs. Check logs for unusual reflection activity if available.
    Affected if HTTP endpoints exist that pass request parameters directly to reflection APIs without validation

A user is affected if they are running any Sitecore product (Commerce, Experience Manager, Experience Platform, or Managed Cloud) with version 9.0 through 10.4 that accepts external input into reflection API calls without validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 10.4 or later
Fixed in 10.4
Interim mitigation

Apply vendor-provided patches for affected Sitecore versions. As an interim measure, review and restrict input handling for reflection-based operations in the application configuration.

Fix this in Experience Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53693 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53693 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data