CVE-2026-2991

KiviCare – Clinic & Patient Management System (EHR) <= 4.1.2 - Unauthenticated Authentication Bypass via Social Login Token

2026-03-17 00:00
Gibran Abdillah

Strategic Overview

Status
Patched in 4.1.3
Affected Version
<= 4.1.2
CVSS
7.3High
Weakness type
CWE-287 · Improper Authentication
CVE
CVE-2026-2991
View all KiviCare – Clinic & Patient Management System (EHR) vulnerabilities

At a glance

CVE-2026-2991 is a high-severity Improper Authentication vulnerability in the KiviCare WordPress plugin, affecting versions <= 4.1.2. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). 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 Gibran Abdillah.

Vulnerability Overview

The KiviCare – Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 4.1.2. This is due to the `patientSocialLogin()` function not verifying the social provider access token before authenticating a user. This makes it possible for unauthenticated attackers to log in as any patient registered on the system by providing only their email address and an arbitrary value for the access token, bypassing all credential verification. The attacker gains access to sensitive medical records, appointments, prescriptions, and billing information (PII/PHI breach). Additionally, authentication cookies are set before the role check, meaning the auth cookies for non-patient users (including administrators) are also set in the HTTP response headers, even though a 403 response is returned.

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-287: Improper Authentication

KiviCare <= 4.1.2 carries this weakness at patientSocialLogin(), and reaching it takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. 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

Related records

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