CVE-2025-59094
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 · uneditedA local privilege escalation vulnerability has been identified in the Kaba exos 9300 System management application (d9sysdef.exe). Within this application it is possible to specify an arbitrary executable as well as the weekday and start time, when the specified executable should be run with SYSTEM privileges.
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 confidenceA local privilege escalation vulnerability exists in the Kaba exos 9300 System management application (d9sysdef.exe) where an authenticated local user can specify an arbitrary executable path along with a weekday and start time, causing the specified executable to run with SYSTEM-level privileges. This allows a standard user to gain complete control over the affected 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
- Local
- Complexity
- Low
- Privileges
- High
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate d9sysdef.exe on the systemSearch for d9sysdef.exe in the Kaba exos 9300 installation directory, typically under Program Files or a vendor-specific path. Use: Get-ChildItem -Path "C:\" -Recurse -Filter "d9sysdef.exe" -ErrorAction SilentlyContinueAffected if The file exists on the system, indicating the vulnerable component is present
-
Check file permissions on d9sysdef.exeRight-click the file, go to Properties > Security, or run: Get-Acl "path\to\d9sysdef.exe" | Select-Object Owner, AccessToString. Verify which users and groups have Write or Full Control permissionsAffected if Non-privileged or non-administrative users have Write or Full Control permissions on the executable, allowing them to replace or modify it
-
Inspect configuration files for d9sysdef.exeLook for accompanying configuration files (e.g., .cfg, .xml, .ini files) in the same directory. Check their permissions using: Get-Acl "path\to\configfile" | Select-Object AccessToStringAffected if Configuration files are writable by non-privileged users, allowing them to specify arbitrary executables to run with SYSTEM privileges
-
Check for scheduled tasks related to d9sysdefRun: Get-ScheduledTask | Where-Object {$_.TaskName -like "*d9sysdef*"} | Get-ScheduledTaskInfo. Note the user account the task runs under and its trigger scheduleAffected if A scheduled task exists that runs d9sysdef.exe with SYSTEM or another elevated account, particularly if triggers are set for specific weekdays and times
-
Verify version against affected rangesRight-click d9sysdef.exe > Properties > Details to view File Version, or run: (Get-Item "path\to\d9sysdef.exe").VersionInfo. Compare this version to any vendor-released version information for exos 9300Affected if The installed version matches or falls within the version range specified by the vendor as vulnerable
You are affected if d9sysdef.exe exists and non-privileged users can modify the executable, its configuration, or its scheduled task settings to execute arbitrary code with SYSTEM privileges.
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 dataApply vendor-supplied patches for the Kaba exos 9300 System management application. Until a patch is available, restrict physical and logical access to systems running this application and monitor for unauthorized scheduled tasks pointing to unexpected executables.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59094 — 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-59094 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