dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2026-1958

HIGH · 8.7 CVSS v4.0 Published 2026-03-23
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 Klinika XP and KlinikaXP Insertino allowed an unauthorized attacker access to several internal services. Critically, this included access to the 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 KlinikaXP: before 5.39.01.01. and KlinikaXP Insertino before 3.1.0.1 Beside removing the hardcoded credentials from the code, previously exposed credentials were also rotated preventing further attack attempts.

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

KlinikaXP and KlinikaXP Insertino contained hard-coded credentials embedded in the application code that provided unauthorized access to internal services, most critically an FTP server hosting software update packages. An attacker with these credentials could upload malicious update files to the FTP server, which would then be distributed and installed on client machines as legitimate updates, enabling remote code execution at scale.

MitigationRemove all hardcoded credentials from source code and implement a secure credential management system (e.g., secrets vault, environment variables, or proper authentication). Rotate any exposed credentials immediately and implement code review processes to prevent future hardcoded secrets.

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. Identify if KlinikaXP is installed
    Search for the KlinikaXP or KlinikaXP Insertino application on the system. Check common installation directories (e.g., Program Files, Program Files (x86)) or use system search to locate the executable or application files.
    Affected if KlinikaXP or KlinikaXP Insertino is found installed on the system.
  2. Search for hardcoded credentials in application files
    Examine application configuration files, .ini files, XML configuration files, and any source code or script files included with the installation. Search for embedded passwords, FTP credentials, or authentication tokens using text search for terms like 'password', 'ftp', 'user', 'pass', 'credential', or 'hardcoded'.
    Affected if Hardcoded credentials, FTP usernames, passwords, or similar secrets are found embedded in configuration or source files.
  3. Inspect FTP server configuration
    Locate and examine any FTP server configuration files within the KlinikaXP installation directory. Look for FTP connection strings, server addresses, credentials, or update server configurations.
    Affected if FTP server credentials or update server configuration with embedded credentials are present.
  4. Examine the update mechanism configuration
    Review files related to the software update functionality. Check for update configuration files that specify where updates are downloaded from, including any FTP servers hosting update packages.
    Affected if An FTP-based update mechanism is configured with stored credentials, or the update configuration references an FTP server.

The environment is affected if KlinikaXP or KlinikaXP Insertino is installed and contains hardcoded FTP or other service credentials in configuration files, as the vulnerability allows unauthorized access to the update distribution server.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove all hardcoded credentials from source code and implement a secure credential management system (e.g., secrets vault, environment variables, or proper authentication). Rotate any exposed credentials immediately and implement code review processes to prevent future hardcoded secrets.

Recommended fix High confidence

KlinikaXP 5.39.01.01 and KlinikaXP Insertino 3.1.0.1

  1. Upgrade KlinikaXP to version 5.39.01.01 or later to receive the fix that removes hardcoded credentials
  2. Upgrade KlinikaXP Insertino to version 3.1.0.1 or later to receive the fix that removes hardcoded credentials
  3. After upgrading, verify that the hardcoded credentials have been removed from the application configuration
  4. Confirm that credentials have been rotated as part of the update process

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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