dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2026-42251

HIGH · 8.7 CVSS v4.0 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Use of hard-coded credentials in KS-SOMED allowed an unauthorized attacker access to FTP server that hosted the application's update packages. The attacker with these credentials could upload a malicious update file, which then may have been distributed and installed on client machines as a legitimate update. This issue affects KS-SOMED with modules: KSPLUPDFTP.exe up to 30.00.00.056 and ANEKSKLIENT.EXE up to 29.00.02.026 Beside removing the hard-coded credentials from the code and changing the update process, access granted by previously exposed credentials was limited to read-only.

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

KS-SOMED contains hard-coded credentials embedded in KSPLUPDFTP.exe (up to 30.00.00.056) and ANEKSKLIENT.EXE (up to 29.00.02.026) that provide unauthorized access to the FTP server hosting application update packages. An attacker with these credentials could potentially upload malicious update files that would be distributed and installed on client machines as legitimate updates.

MitigationRemove all hard-coded credentials from the application code and implement secure credential management (e.g., environment variables, secure vault, or prompt-based authentication). Additionally, redesign the update distribution process to use secure, authenticated channels with integrity verification.

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: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. Locate KSPLUPDFTP.exe and determine its version
    Search for KSPLUPDFTP.exe in installation directories (commonly in program files or application data folders for KS-SOMED) and retrieve file properties to read the version number. Use PowerShell: Get-ChildItem -Path 'C:\' -Recurse -Filter 'KSPLUPDFTP.exe' -ErrorAction SilentlyContinue | Select-Object FullName, VersionInfo
    Affected if Version is 30.00.00.056 or lower (including any version up to 30.00.00.056)
  2. Locate ANEKSKLIENT.EXE and determine its version
    Search for ANEKSKLIENT.EXE in installation directories and retrieve file properties to read the version number. Use PowerShell: Get-ChildItem -Path 'C:\' -Recurse -Filter 'ANEKSKLIENT.EXE' -ErrorAction SilentlyContinue | Select-Object FullName, VersionInfo
    Affected if Version is 29.00.02.026 or lower (including any version up to 29.00.02.026)
  3. Verify update functionality is configured or active
    Check for configuration files or registry entries indicating the FTP update feature is enabled. Look for update server URLs, FTP connection settings, or scheduled tasks related to KS-SOMED or ANEKSKLIENT auto-update.
    Affected if The update feature is enabled, configured to connect to an update server, or scheduled to run automatically
  4. Review update server configuration for hardcoded credentials
    Examine configuration files, INI files, XML configs, or embedded settings within the executable that contain FTP server credentials (username/password). Search for strings like 'ftp://' or 'update' in config files in the application directory.
    Affected if Hardcoded FTP credentials (username and password) are found in configuration files or embedded within the application

You are affected if either KSPLUPDFTP.exe version 30.00.00.056 or lower OR ANEKSKLIENT.EXE version 29.00.02.026 or lower is present AND the FTP update feature is enabled or configured.

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

Remove all hard-coded credentials from the application code and implement secure credential management (e.g., environment variables, secure vault, or prompt-based authentication). Additionally, redesign the update distribution process to use secure, authenticated channels with integrity verification.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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