CVE-2025-59091
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 · uneditedMultiple hardcoded credentials have been identified, which are allowed to sign-in to the exos 9300 datapoint server running on port 1004 and 1005. This server is used for relaying status information from and to the Access Managers. This information, among other things, is used to graphically visualize open doors and alerts. However, controlling the Access Managers via this interface is also possible. To send and receive status information, authentication is necessary. The Kaba exos 9300 application contains hard-coded credentials for four different users, which are allowed to login to the datapoint server and receive as well as send information, including commands to open arbitrary doors.
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 · moderate confidenceThe Kaba exos 9300 datapoint server (ports 1004/1005) contains four hardcoded credentials that provide full authentication to the Access Manager relay system. An attacker with network access can use these credentials to view door status and send commands to open arbitrary doors, achieving complete control over the physical access control system.
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:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Kaba exos 9300 installationCheck your system inventory or running services for 'Kaba exos 9300' or 'datapoint server' software. On Windows, check installed programs; on Linux, check package managers or running processes.Affected if The Kaba exos 9300 datapoint server software is installed on the system.
-
Verify datapoint server ports are openRun 'netstat -an | grep -E "1004|1005"' or use a port scanner (nmap -p 1004,1005 <target>) to check if ports 1004 and/or 1005 are listening.Affected if Ports 1004 or 1005 are open and listening, indicating the datapoint server is active.
-
Check network accessibility of datapoint portsDetermine if ports 1004/1005 are reachable from networks outside your trusted internal network. Use 'nmap -p 1004,1005 -sV <target>' or check firewall rules and network segments.Affected if The datapoint server ports are accessible from untrusted or external networks, not just from trusted management stations.
-
Verify credential management statusIf you have administrative access to the Access Manager relay system, check whether the default credentials for the datapoint server have been changed. Compare any configured credentials against vendor documentation for default values.Affected if The default hardcoded credentials remain unchanged or the system is using the built-in authentication without custom credential rotation.
You are affected if the Kaba exos 9300 datapoint server is running with ports 1004/1005 exposed to network segments where untrusted users could access the hardcoded authentication credentials.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImmediately network-segment the datapoint server to limit exposure, change any default credentials if possible, contact vendor for firmware/security patch to remove hardcoded credentials, and implement proper credential management with rotating credentials.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59091 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59091 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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