CVE-2026-2992

KiviCare <= 4.1.2 - Missing Authorization to Unauthenticated Privilege Escalation via Setup Wizard

2026-03-17 00:00
Athiwat Tiprasaharn (Jitlada)

Strategic Overview

Status
Patched in 4.1.3
Affected Plugin
KiviCare – Clinic & Patient Management System (EHR)
Affected Version
<= 4.1.2
CVSS
8.2High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-2992
View all KiviCare – Clinic & Patient Management System (EHR) vulnerabilities

At a glance

CVE-2026-2992 is a high-severity Missing Authorization vulnerability in the KiviCare WordPress plugin, affecting versions <= 4.1.2. It carries a CVSS score of 8.2 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 4.1.3; sites on affected versions should update now. Disclosed March 2026, reported by Athiwat Tiprasaharn (Jitlada).

Vulnerability Overview

The KiviCare – Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to Privilege Escalation due to missing authorization on the `/wp-json/kivicare/v1/setup-wizard/clinic` REST API endpoint in all versions up to, and including, 4.1.2. This makes it possible for unauthenticated attackers to create a new clinic and a WordPress user with clinic admin privileges.

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. A successful exploit has high impact on integrity.

CWE-862: Missing Authorization

Reaching this weakness in KiviCare <= 4.1.2 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.1.3: builds <= 4.1.2 are affected, anything from 4.1.3 onward is not.

Remediation

Update to version 4.1.3, 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.1.3 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-2992https://www.wordfence.com/threat-intel/vulnerabilities/id/d96743ea-08b1-4b4c-9d62-558b97a6e297https://nvd.nist.gov/vuln/detail/CVE-2026-2992

Related records

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