CVE-2025-2746
Kentico Xperience CMS Authentication Bypass Using an Alternate Path or Channel Vulnerability
Kentico Xperience CMS
An authentication bypass vulnerability in Kentico Xperience allows authentication bypass via the Staging Sync Server password handling of empty SHA1 usernames in digest authentication. Authentication bypass allows an attacker to control administrative objects.This issue affects Xperience through 13.0.172.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 20 October 2025. US federal agencies were required to remediate it by 10 November 2025.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 73.6%, which is higher than 99.5% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2025-2746 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2025-2746.
What does CVE-2025-2746 affect?
CVE-2025-2746 affects Kentico Xperience CMS. An authentication bypass vulnerability in Kentico Xperience allows authentication bypass via the Staging Sync Server password handling of empty SHA1 usernames in digest authentication. Authentication bypass allows an attacker to control administrative objects.This issue affects Xperience through 13.0.172.
How severe is CVE-2025-2746?
CVE-2025-2746 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 73.6%, higher than 99.5% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 10 November 2025.
How should organisations respond to CVE-2025-2746?
Apply the vendor patch for Kentico Xperience CMS as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.