CVE-2026-40792

KiviCare – Clinic & Patient Management System (EHR) <= 4.2.1 - Authenticated (Subscriber+) Insecure Direct Object Reference

2026-04-23 00:00
Jakub Herman

Strategic Overview

Status
Patched in 4.3.0
Affected Version
<= 4.2.1
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-40792
View all KiviCare – Clinic & Patient Management System (EHR) vulnerabilities

At a glance

CVE-2026-40792 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the KiviCare WordPress plugin, affecting versions <= 4.2.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.3.0; sites on affected versions should update now. Disclosed April 2026, reported by Jakub Herman.

Vulnerability Overview

The KiviCare – Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 4.2.1 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform an unauthorized action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in KiviCare <= 4.2.1 takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For KiviCare the fix is 4.3.0: builds <= 4.2.1 are affected, anything from 4.3.0 onward is not.

Remediation

Update to version 4.3.0, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: KiviCare 4.3.0 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C