CVE-2025-59097
CriticalSummary
The exos 9300 application configures Access Managers via a GUI. When saving, the whole configuration is sent via SOAP without any authentication or authorization by default. Optional security (IPsec, mTLS) is not enabled by default.
Risk Assessment
An attacker with network access can fully control the environment, e.g., open doors, change alarm configurations, and inputs/outputs, without authentication.
Recommendation
Enable authentication and authorization (IPsec or mTLS) for SOAP communication and restrict network access to the exos 9300 server.
Other vulnerabilities in exos 9300
See all- CVE-2025-59093High
The vulnerability in Exos 9300 involves a randomly generated database password for MSSQL, derived from static random values concatenated with the hostname and a random string readable from the registry by any user. This allows an attacker to derive the password and gain authenticated access to the central database as user Exos9300Common.
- CVE-2025-59092High
An RPC service in exos 9300, run by FSMobilePhoneInterface.exe, is reachable on port 4000 and requires no authentication. This allows sending arbitrary status information, e.g., about door contacts, without prior login.
- CVE-2025-59091Critical
Multiple hardcoded credentials allow login to the exos 9300 datapoint server on ports 1004 and 1005. This server relays status information and can also control Access Managers, including opening doors.
- CVE-2025-59090Critical
The exos 9300 server exposes a SOAP API on port 8002 without authentication. This allows network attackers to create arbitrary access log events and query 2FA PINs associated with enrolled chip cards.
Original NVD description (English source)
The exos 9300 application can be used to configure Access Managers (e.g. 92xx, 9230 and 9290). The configuration is done in a graphical user interface on the dormakaba exos server. As soon as the save button is clicked in exos 9300, the whole configuration is sent to the selected Access Manager via SOAP. The SOAP request is sent without any prior authentication or authorization by default. Though authentication and authorization can be configured using IPsec for 92xx-K5 devices and mTLS for 92xx-K7 devices, it is not enabled by default and must therefore be activated with additional steps. This insecure default allows an attacker with network level access to completely control the whole environment. An attacker is for example easily able to conduct the following tasks without prior authentication: - Re-configure Access Managers (e.g. remove alarming system requirements) - Freely re-configure the inputs and outputs - Open all connected doors permanently - Open all doors for a defined t