CVE-2025-59092
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 · uneditedAn RPC service, which is part of exos 9300, is reachable on port 4000, run by the process FSMobilePhoneInterface.exe. This service is used for interprocess communication between services and the Kaba exos 9300 GUI, containing status information about the Access Managers. Interacting with the service does not require any authentication. Therefore, it is possible to send arbitrary status information about door contacts etc. without prior authentication.
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 confidenceAn unauthenticated RPC service (FSMobilePhoneInterface.exe) running on port 4000 in Kaba exos 9300 access control systems allows remote attackers to send arbitrary status information about door contacts and Access Managers without any authentication. This enables manipulation of access control system status data.
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:N/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 systemCheck system inventory or physically verify the access control hardware model is Kaba exos 9300Affected if The system is NOT a Kaba exos 9300 device - different models are not affected by this specific CVE
-
Verify port 4000 is listeningRun 'netstat -an | findstr :4000' or 'nmap -p 4000 <target>' to check if port 4000 is open and accepting connectionsAffected if Port 4000 is open and bound to a service - the RPC service is exposed
-
Confirm FSMobilePhoneInterface.exe is runningOn the access control server, run 'tasklist | findstr FSMobilePhoneInterface' or check running services for FSMobilePhoneInterfaceAffected if The FSMobilePhoneInterface.exe process is running - the vulnerable component is active
-
Test unauthenticated RPC accessAttempt to connect to the RPC service on port 4000 using a tool like rpcclient or netcat: 'nc -nv <target> 4000' and send a raw RPC request without providing credentialsAffected if Connection succeeds and returns door contact or Access Manager status data without authentication - the vulnerability is present and exploitable
-
Review network exposureCheck firewall rules or network segmentation: 'netsh advfirewall firewall show rule name=all' or review network ACLs to determine if port 4000 is accessible from untrusted networksAffected if Port 4000 is accessible from external or untrusted network segments - the system is at risk of remote exploitation
You are affected if you run a Kaba exos 9300 system with FSMobilePhoneInterface.exe listening on port 4000 and that port is accessible from any network where untrusted actors exist, because the service accepts unauthenticated status queries.
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 dataRestrict network access to port 4000 through firewall rules or network segmentation to prevent unauthorized access to the RPC service, limiting exposure to trusted internal systems only.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59092 — 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-59092 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