XperienceApplication · Kentico

CVE-2025-2794

HIGH · 8.7 CVSS v4.0 Published 2025-03-31
Fix available
A fix is available. Upgrade to after 13.0.180 or later.
See remediation →
96/100
Remediation priority · Urgent
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
An unsafe reflection vulnerability in Kentico Xperience allows an unauthenticated attacker to kill the current process, leading to a Denial-of-Service condition. This issue affects Xperience: through 13.0.180.

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

Kentico Xperience contains an unsafe reflection vulnerability that allows unauthenticated attackers to manipulate reflection operations, enabling them to terminate the application process and cause a Denial-of-Service condition. This affects versions through 13.0.180.

MitigationApply the vendor patch for CVE-2025-2794 which addresses unsafe reflection by implementing proper input validation on reflection calls. Until patched, consider network-level restrictions or a WAF rule to limit attack surface.

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
XperienceApplication
Affected:<= 13.0.180

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm Kentico Xperience is installed
    Look for Kentico Xperience by accessing the administration interface (typically at /CMSModules/ or /CMSPages/ paths) or checking for Kentico DLLs in the application's bin directory
    Affected if The application is running Kentico Xperience software
  2. Determine the installed version
    Log into the Kentico Xperience administration panel and navigate to the About section (Help > About) or check the version in the system's administration interface
    Affected if The version number is 13.0.180 or lower
  3. Verify the application is network-accessible
    Confirm the Kentico Xperience web application is accessible over the network (not localhost-only)
    Affected if The application is externally accessible and the version is 13.0.180 or lower
  4. Check for reflection-based endpoints
    Review the application's exposed HTTP endpoints, particularly those that may invoke System.Reflection APIs without proper validation
    Affected if Reflection-enabled endpoints are exposed and the version is unpatched

The environment is affected if Kentico Xperience version 13.0.180 or lower is running and is network-accessible, since the unsafe reflection vulnerability allows unauthenticated remote attackers to cause denial of service.

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 a release after 13.0.180
Interim mitigation

Apply the vendor patch for CVE-2025-2794 which addresses unsafe reflection by implementing proper input validation on reflection calls. Until patched, consider network-level restrictions or a WAF rule to limit attack surface.

Fix this in Xperience Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2794 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