Advisory

Cisco patches critical hardcoded credentials vulnerability in Unified Communications Manager

Take action: Obvious first step - isolate the SSH port of your CUCM and make it accessible from trusted networks only. Then VERY QUICLY update to versions 15.0.1.13010-1 through 15.0.1.13017-1, or apply the patches. Just isolating the CUCM isn't enough - the hardcoded password can be abused by malicious insiders, or other devices with access to trusted networks can be breached and the attackers can then breach CUCM.


Learn More

Cisco is reporting a critical vulnerability in its Unified Communications Manager (Unified CM) and Unified Communications Manager Session Management Edition (Unified CM SME) that could allow unauthenticated remote attackers to gain complete administrative control of affected systems. 

Cisco Unified Communications Manager is the central control system for enterprise IP telephony networks, managing call routing, device configuration, and telephony features across organizations.

The vulnerability is tracked as CVE-2025-20309 (CVSS score 10.0) - hardcoded static SSH credentials for the root account. These credentials were supposedly used during development but were inadvertently left in production releases. The static user credentials for the root account cannot be changed or deleted through normal administrative procedures. Unless the systems are patched, there is a persistent backdoor.

Successful exploitation could allow attackers to monitor calls, manipulate call routing, access sensitive configuration data, or use the compromised system as a starting point for lateral movement within corporate networks.

The vulnerability affects Cisco Unified CM and Unified CM SME Engineering Special (ES) versions 15.0.1.13010-1 through 15.0.1.13017-1, regardless of device configuration or security settings.

Cisco has released fixes to address this vulnerability. Customers can pgrade to Cisco Unified CM and Unified CM SME 15SU3 (scheduled for July 2025) or apply the patch file ciscocm.CSCwp27755_D0247-1.cop.sha512. T

There is no workaround available.

Successful exploitation attempts would generate log entries in /var/log/active/syslog/secure showing SSH login sessions for the root user. Since this logging is enabled by default, administrators can check for potential compromise by running the command file get activelog syslog/secure from the CLI and examining the logs for unauthorized root access attempts.

Cisco patches critical hardcoded credentials vulnerability in Unified Communications Manager