dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-15065

MEDIUM · 6.3 CVSS v3.1 Published 2025-12-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/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
Exposure of Sensitive Information to an Unauthorized Actor, Missing Encryption of Sensitive Data, Files or Directories Accessible to External Parties vulnerability in Kings Information & Network Co. KESS Enterprise on Windows allows Privilege Escalation, Modify Existing Service, Modify Shared File.This issue affects KESS Enterprise: before *.25.9.19.exe

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 confidence

KESS Enterprise on Windows contains a vulnerability allowing unauthorized access to sensitive information due to missing encryption and improper file/directory access controls. This exposure can be exploited to achieve privilege escalation, modify existing Windows services, or alter shared files. The issue affects versions prior to *.25.9.19.exe.

MitigationUpdate KESS Enterprise to version *.25.9.19.exe or later. Additionally, review and harden file permissions on the application directory and ensure any sensitive data or configuration files are properly encrypted.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

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 KESS Enterprise installation
    Search for KESS Enterprise on the Windows system by checking Program Files, Program Files (x86), or using the 'Get-ItemProperty' cmdlet for installed software in the Windows Registry under HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall
    Affected if KESS Enterprise is found installed on the system
  2. Determine installed version
    Locate the KESS Enterprise executable or check the installed version in the Windows Registry (DisplayVersion value) and compare it to the affected version threshold *.25.9.19.exe - any version lower than this threshold is affected
    Affected if The installed version is any version prior to *.25.9.19.exe (e.g., *.25.x.x, *.24.x.x, etc.)
  3. Inspect file permissions on application directory
    Use 'icacls' or 'Get-Acl' cmdlet on the KESS Enterprise installation directory to list all user/group permissions and identify if non-privileged users have read, write, or modify access to sensitive directories
    Affected if Users without proper authorization can read, write, or modify files within the KESS Enterprise application directory
  4. Check for unencrypted sensitive files
    Examine the KESS Enterprise installation folder and subfolders for configuration files, database files, or data files that may contain sensitive information and are stored without encryption (look for .ini, .xml, .mdb, .db, .dat, or plaintext log files)
    Affected if Sensitive configuration files, credentials, or data files are stored in plaintext or without encryption within the application directory
  5. Verify access to shared files and services
    Check if the KESS Enterprise application directory contains files accessible from shared network locations or if the application modifies Windows services that could be altered by low-privilege users
    Affected if Shared files or Windows service configurations related to KESS Enterprise can be modified by unauthorized users

The environment is affected if KESS Enterprise is installed with a version prior to *.25.9.19.exe and exhibits any of the permission weaknesses or unencrypted data exposure issues described above.

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

Update KESS Enterprise to version *.25.9.19.exe or later. Additionally, review and harden file permissions on the application directory and ensure any sensitive data or configuration files are properly encrypted.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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