dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-59097

CRITICAL · 9.3 CVSS v4.0 Published 2026-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
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 time interval - Change the admin password - and many more Network level access can be gained due to an insufficient network segmentation as well as missing LAN firewalls. Devices with an insecure configuration have been identified to be directly exposed to the internet.

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 · high confidence

The exos 9300 application sends configuration to Access Managers via SOAP without any authentication or authorization by default. An attacker with network-level access can send SOAP requests to completely control the physical security infrastructure, including opening doors, reconfiguring I/O, changing admin passwords, and disabling alarm systems.

MitigationEnable IPsec (for 92xx-K5) or mTLS (for 92xx-K7) authentication and implement proper network segmentation with firewalls to restrict access to trusted networks only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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:H/VI:H/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. Identify if exos 9300 is installed
    Check for the presence of the exos 9300 application or service on the system. Look for processes named 'exos', '9300', or related physical security software in running processes or installed programs.
    Affected if The exos 9300 application is present and running on the system.
  2. Locate the SOAP endpoint
    Identify the network service listening for SOAP requests. Common ports for physical security SOAP interfaces include 80, 443, 8080, or 8443. Check open ports and running services to identify the SOAP endpoint URL.
    Affected if A SOAP service endpoint is exposed and listening for requests.
  3. Test SOAP access without credentials
    Send an unauthenticated SOAP request to the identified endpoint (e.g., using curl or a SOAP client). Observe if the request is accepted and processed without requiring any authentication headers, certificates, or credentials.
    Affected if The SOAP interface accepts and processes requests without any authentication token, certificate, or credentials.
  4. Check if IPsec is enabled (for 92xx-K5 models)
    For Access Manager models 92xx-K5, verify IPsec configuration. Check if IPsec tunnels are established and active between the exos 9300 server and Access Managers. Look for IPsec status in system configuration or network settings.
    Affected if IPsec is not enabled or not properly configured for 92xx-K5 models, and the SOAP interface is accessible over the network.
  5. Check if mTLS is enabled (for 92xx-K7 models)
    For Access Manager models 92xx-K7, verify that mutual TLS (client certificate) authentication is required. Check if the SOAP endpoint requires a valid client certificate for connection. Inspect SSL/TLS configuration settings.
    Affected if mTLS is not enabled or not properly configured for 92xx-K7 models, and the SOAP interface accepts connections without client certificate verification.

A user is affected if the exos 9300 application is running with its SOAP interface exposed on the network without authentication (IPsec for 92xx-K5 or mTLS for 92xx-K7) enabled.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable IPsec (for 92xx-K5) or mTLS (for 92xx-K7) authentication and implement proper network segmentation with firewalls to restrict access to trusted networks only.

Recommended fix Moderate confidence
  1. Review the dormakaba exos 9300 configuration interface to identify the authentication settings for your Access Manager model
  2. For 92xx-K5 devices: Enable IPsec authentication in the configuration settings before saving configuration to Access Managers
  3. For 92xx-K7 devices: Enable mTLS (mutual TLS) authentication in the configuration settings before saving configuration to Access Managers
  4. Verify that authentication is enforced by attempting an unauthenticated SOAP request after enabling - it should be rejected
  5. Ensure network segmentation is in place to limit exposure of the Access Manager management interfaces to untrusted networks
  6. If devices are exposed to the internet, implement firewall rules to restrict access to trusted IP addresses only
  7. Document the enabled authentication configuration for compliance and audit purposes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing10.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,660
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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