CVE-2026-13612

KiviCare – Clinic & Patient Management System (EHR) < 4.5.2 - Authenticated (Custom role+) Information Exposure

2026-08-13 00:00
Sai Praneeth Koti

Strategic Overview

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

At a glance

CVE-2026-13612 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the KiviCare WordPress plugin, affecting versions < 4.5.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Custom role level or above. The issue is fixed in version 4.5.2; sites on affected versions should update now. Disclosed August 2026, reported by Sai Praneeth Koti.

Vulnerability Overview

The KiviCare – Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to 4.5.2. This makes it possible for authenticated attackers, with custom role-level access and above, to extract sensitive user or configuration data.

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.5.2 takes an account at Custom role 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.5.2: builds < 4.5.2 are affected, anything from 4.5.2 onward is not.

Remediation

Update to version 4.5.2, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: KiviCare 4.5.2 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