CVE-2026-11990

KiviCare <= 4.4.0 - Missing Authorization to Unauthenticated Payment Bypass and Appointment Status Manipulation via /payment-success REST Endpoint

2026-07-09 20:52
Niv Kochan

Strategic Overview

Status
Patched in 4.5.0
Affected Plugin
KiviCare – Clinic & Patient Management System (EHR)
Affected Version
<= 4.4.0
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-11990
View all KiviCare – Clinic & Patient Management System (EHR) vulnerabilities

At a glance

CVE-2026-11990 is a medium-severity Missing Authorization vulnerability in the KiviCare WordPress plugin, affecting versions <= 4.4.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.5.0; sites on affected versions should update now. Disclosed July 2026, reported by Niv Kochan.

Vulnerability Overview

The KiviCare – Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.4.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to mark arbitrary pending appointments as Confirmed and forge an associated completed payment record in wp_kc_payments_appointment_mappings using an attacker-supplied payment ID, bypassing payment entirely. This exploit is achievable on a default installation because the gateway resolution logic returns all registered gateways regardless of admin-enabled status, making the manual (KCPayLater) gateway always selectable.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in KiviCare <= 4.4.0 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For KiviCare the fix is 4.5.0: builds <= 4.4.0 are affected, anything from 4.5.0 onward is not.

Remediation

Update to version 4.5.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: KiviCare 4.5.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-11990https://www.wordfence.com/threat-intel/vulnerabilities/id/efe4223a-5c1a-401e-a46b-0278e96d2d71https://nvd.nist.gov/vuln/detail/CVE-2026-11990

Related records

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