dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-59095

MEDIUM · 6.8 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 →
70/100
Remediation priority · Elevated
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 program libraries (DLL) and binaries used by exos 9300 contain multiple hard-coded secrets. One notable example is the function "EncryptAndDecrypt" in the library Kaba.EXOS.common.dll. This algorithm uses a simple XOR encryption technique combined with a cryptographic key (cryptoKey) to transform each character of the input string. However, it's important to note that this implementation does not provide strong encryption and should not be considered secure for sensitive data. It's more of a custom encryption approach rather than a common algorithm used in cryptographic applications. The key itself is static and based on the founder's name of the company. The functionality is for example used to encrypt the user PINs before storing them in the MSSQL database.

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 uses a weak custom XOR-based encryption algorithm in the Kaba.EXOS.common.dll library to protect sensitive data. The cryptographic key is hard-coded and static, derived from the company founder's name, and is used to encrypt user PINs before storage in MSSQL databases. This provides essentially no security as XOR encryption is trivially reversible and the static key exposes all encrypted data across all deployments.

MitigationReplace the XOR-based encryption with a proper symmetric algorithm (e.g., AES-256-GCM) using cryptographically secure random keys per installation, implement secure key management or a key vault, and rotate any keys that may have been exposed.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if exos 9300 application is installed
    Check system for presence of exos 9300 application files, typically found in program directories or application-specific installation folders. Look for folders containing 'exos' or '9300' in the name.
    Affected if The exos 9300 application is present on the system
  2. Locate Kaba.EXOS.common.dll library
    Search for the file Kaba.EXOS.common.dll within the exos 9300 installation directory. Common locations include application bin folders or shared library directories.
    Affected if Kaba.EXOS.common.dll exists in the exos installation directory
  3. Verify XOR encryption is in use
    Inspect the Kaba.EXOS.common.dll library for XOR-based encryption routines or functions. This may require disassembling the DLL or checking application logs/code references that import this library. Look for patterns such as XOR operations on byte arrays used for encryption routines.
    Affected if The application uses Kaba.EXOS.common.dll for encrypting sensitive data like user PINs
  4. Check MSSQL database for encrypted PIN storage
    Query the MSSQL database used by exos 9300 for tables storing user PINs or similar sensitive fields. Examine the stored data patterns - XOR encrypted data often has recognizable characteristics.
    Affected if User PINs or similar credentials are stored in the MSSQL database in a pattern consistent with XOR encryption
  5. Confirm hard-coded static key presence
    Analyze the Kaba.EXOS.common.dll for hard-coded key values used in encryption routines. Static XOR keys derived from company founder names or other constant strings will be embedded in the binary.
    Affected if A static, hard-coded key is found embedded in the Kaba.EXOS.common.dll library code

Your environment is affected if the exos 9300 application is installed, uses Kaba.EXOS.common.dll for encrypting user PINs with XOR-based encryption, and stores these PINs in an MSSQL database using a hard-coded static key.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace the XOR-based encryption with a proper symmetric algorithm (e.g., AES-256-GCM) using cryptographically secure random keys per installation, implement secure key management or a key vault, and rotate any keys that may have been exposed.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59095 — 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-59095 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