Skip to content
Server Security Center
KEVcritical9.8

CVE-2025-2747: Kentico Xperience CMS Authentication Bypass Using an Alternate Path or Channel

Kentico Xperience CMS · listed in the CISA catalog of actively exploited vulnerabilities since 2025-10-20.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
97%
higher than 99.8% of all CVEs
Added to CISA KEV
2025-10-20
US federal due date 2025-11-10
Automatable (CISA SSVC)
yes
technical impact: total

What is CVE-2025-2747?

An authentication bypass vulnerability in Kentico Xperience allows authentication bypass via the Staging Sync Server component password handling for the server defined None type. Authentication bypass allows an attacker to control administrative objects.This issue affects Xperience through 13.0.178.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Kentico XperienceStaging
    Affected
    • ≤ 13.0.178
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: devnet.kentico.com/download/hotfixes
  • CISA's deadline for US federal agencies: 2025-11-10 (passed) – a useful benchmark for everyone else, too.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-288 Authentication Bypass Using an Alternate Path or Channel

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.