KiviCare – Clinic & Patient Management System (EHR) <= 2.3.8 - SQL Injection
Strategic Overview
- Status
- Patched in 2.3.9
- Affected Plugin
- KiviCare – Clinic & Patient Management System (EHR)
- Affected Version
<= 2.3.8- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2022-0786
At a glance
CVE-2022-0786 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the KiviCare WordPress plugin, affecting versions <= 2.3.8. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.3.9; sites on affected versions should update now. Disclosed May 2022, reported by cydave.
Vulnerability Overview
The KiviCare WordPress plugin before 2.3.9 does not sanitise and escape some parameters before using them in SQL statements via the ajax_post AJAX action with the get_doctor_details route, leading to SQL Injections exploitable by unauthenticated users
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 confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in KiviCare <= 2.3.8 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For KiviCare the fix is 2.3.9: builds <= 2.3.8 are affected, anything from 2.3.9 onward is not.
Remediation
Update to version 2.3.9, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to KiviCare: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: KiviCare 2.3.9 closes this, and updating the plugin is the step that ends it.
- Firewall
- 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 - 8.2CVE-2026-2992: KiviCare <= 4.1.2 Unauthenticated Privilege Escalation
CVE-2026-2992 - 7.3CVE-2026-2991: KiviCare Authentication Bypass
CVE-2026-2991 - 6.5CVE-2026-15073: KiviCare <= 4.5.0 SQL Injection
CVE-2026-15073 - 6.5CVE-2026-25022: KiviCare <= 3.6.16 SQL Injection
CVE-2026-25022 - 6.5CVE-2025-66095: KiviCare <= 3.6.13 SQL Injection
CVE-2025-66095 - 6.5CVE-2025-1572: KiviCare SQL Injection
CVE-2025-1572 - 6.5CVE-2024-11730: KiviCare SQL Injection
CVE-2024-11730
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C