KiviCare – Clinic & Patient Management System (EHR) <= 3.2.0 - Missing Authorization
Strategic Overview
- Status
- Patched in 3.2.1
- Affected Plugin
- KiviCare – Clinic & Patient Management System (EHR)
- Affected Version
<= 3.2.0- CVSS
- 5.4Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-2627
At a glance
CVE-2023-2627 is a medium-severity Missing Authorization vulnerability in the KiviCare WordPress plugin, affecting versions <= 3.2.0. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.2.1; sites on affected versions should update now. Disclosed June 2023, reported by Erwan LR.
Vulnerability Overview
The KiviCare – Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to unauthorized access to and modification of data due to missing capability checks on multiple AJAX functions in versions up to, and including, 3.2.0. This makes it possible for authenticated attackers with subscriber-level privileges or above to modify plugin settings including adding arbitrary clinics, doctors, receptionists, and appointment as well as viewing plugin configuration.
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-862: Missing Authorization
Reaching this weakness in KiviCare <= 3.2.0 takes a caller who can reach the endpoint. 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 3.2.1: builds <= 3.2.0 are affected, anything from 3.2.1 onward is not.
Remediation
Update to version 3.2.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: KiviCare 3.2.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in KiviCare – Clinic & Patient Management System (EHR)
- 9.8CVE-2026-13610: KiviCare Privilege Escalation
CVE-2026-13610 - 9.8CVE-2022-0786: KiviCare SQL Injection
CVE-2022-0786 - 7.5CVE-2024-11728: KiviCare SQL Injection
CVE-2024-11728 - 7.3CVE-2026-2991: KiviCare Authentication Bypass
CVE-2026-2991 - 6.5CVE-2026-15453: KiviCare <= 4.5.1 SQL Injection
CVE-2026-15453 - 6.5CVE-2026-13613: KiviCare <= 4.5.1 SQL Injection
CVE-2026-13613 - 6.5CVE-2026-15072: KiviCare <= 4.5.0 SQL Injection
CVE-2026-15072 - 6.5CVE-2026-15073: KiviCare <= 4.5.0 SQL Injection
CVE-2026-15073
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C