Skip to main content

KiviCare EUVDEUVD-2026-57077

| CVE-2026-13613 HIGH
SQL Injection (CWE-89)
2026-08-12 WPScan GHSA-6rg5-hf6w-rc4q
8.8
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain or compromise clinic staff credentials
  2. Delivery
    Authenticate to WordPress with staff role
  3. Exploit
    Send crafted HTTP request to vulnerable KiviCare endpoint
  4. Execution
    Inject SQL payload into unsanitized parameter
  5. Persist
    Execute arbitrary SQL query against WordPress database
  6. Impact
    Exfiltrate patient records and wp_users credential hashes

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated WordPress session with at minimum a clinic staff-level role granted by the KiviCare plugin - unauthenticated external attackers cannot directly exploit this vulnerability. The attacker must interact with the specific KiviCare plugin endpoint(s) where unsanitized parameters are passed to SQL queries; no additional non-default configuration beyond having the KiviCare plugin installed and active is required. Limiting factors: the clinic staff role requirement (PR:L) means mass unauthenticated scanning cannot directly exploit this; sites that have granted no external users clinic staff privileges, or that restrict the WordPress admin and login interface to trusted networks, have substantially reduced exposure. Insider threat and credential-compromise scenarios (phishing, brute force, password reuse) are the realistic prerequisite attack paths.

Impact

The CVSS 8.8 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects a network-exploitable flaw requiring only low-privilege authentication with full confidentiality, integrity, and availability impact - consistent with classic authenticated SQLi. The 17% EPSS score is notably elevated for a WordPress plugin CVE, placing it in the upper tier of exploitation likelihood and suggesting meaningful automated or opportunistic targeting potential. A publicly available POC (reported via WPScan exploit reference) further compresses the time-to-exploit window. The critical limiting factor is the requirement for a clinic staff-level WordPress account: this blocks fully unauthenticated mass exploitation but does not eliminate risk from insider threats, phished credentials, or brute-forced accounts. No CISA KEV listing is present, so active exploitation in the wild is not confirmed - but the POC and EPSS signal together suggest this should be treated as actively targeted imminently if not already.

Exploit ScenarioDerived

An attacker who holds or has obtained a clinic staff-level WordPress account crafts an HTTP request embedding SQL payloads into a KiviCare plugin parameter - for example, a patient search or appointment field. Because the plugin passes this input unsanitized into a SQL query, the attacker can use UNION-based or blind SQL injection techniques to extract the full WordPress database, including wp_users password hashes, patient records, and any stored credentials. A publicly available POC from WPScan lowers the skill bar significantly, making scripted exploitation feasible for low-sophistication threat actors.

Act Now Prioritize within 24-48h. Why: HIGH severity + EPSS > 10%.
Patch available 17.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 12, 2026

SQL injection in the KiviCare WordPress plugin (all versions before 4.5.2) enables authenticated clinic staff users to execute arbitrary SQL against the underlying WordPress database. Unsanitized user-supplied parameters are passed directly into SQL queries, granting an attacker full read, write, and delete access to database contents including patient records and credentials. With a publicly available proof-of-concept, an EPSS of 17%, and a CVSS of 8.8, this is a high-priority patch for any healthcare-sector WordPress deployment running this plugin - though no CISA KEV-confirmed active exploitation has been identified at time of analysis.

RemediationAI

Update the KiviCare WordPress plugin to version 4.5.2 or later immediately - this is the vendor-released patch confirmed by the WPScan advisory at https://wpscan.com/vulnerability/76b7d66f-6fa3-41e1-9216-ec125e34ade9/. If patching is not immediately possible, restrict clinic staff role assignment to only fully trusted accounts and audit existing staff-role users for any unauthorized additions. As a compensating control, deploy a WAF with SQL injection signature rules (e.g., ModSecurity CRS) in front of the WordPress instance - note this may generate false positives on legitimate KiviCare form submissions and requires tuning. Additionally, enable WordPress login rate-limiting and two-factor authentication on all staff accounts to reduce credential-compromise risk, which is the prerequisite attack path. Monitor database slow-query logs and WAF alerts for anomalous SQL patterns targeting KiviCare endpoints.

Affected VersionsENISA

KiviCare 0 <4.5.2

Affected Packages

euvd kivicare fix: 4.5.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

KiviCare is a WordPress plugin designed for healthcare clinic management, handling patient appointments, staff roles, and clinic records. The root cause is CWE-89 (Improper Neutralization of Special Elements in an SQL Command): user-controlled input is concatenated into SQL queries without parameterization or adequate escaping, a classic and well-understood vulnerability class. The affected CPE is cpe:2.3:a:unknown:kivicare:*:*:*:*:*:*:*:* for all versions prior to 4.5.2, with the vendor field listed as 'unknown' in NVD CPE data - indicating incomplete upstream enrichment. Because WordPress plugins execute in a shared PHP/MySQL environment, successful SQL injection here can expose the entire WordPress database, including wp_users hashes, plugin option tables, and any healthcare data stored by KiviCare.

Know when Kivicare gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-exploitable over HTTP with low-privilege clinic staff auth required; no user interaction; full CIA impact on the WordPress database; scope unchanged as plugin operates within the same trust boundary.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Aug 12, 2026 - 20:22 NVD
8.8 (HIGH)
Patch available
Aug 12, 2026 - 07:16 EUVD
CVE Published
Aug 12, 2026 - 06:00 cve.org
HIGH 8.8
CVE Published
Aug 12, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The KiviCare WordPress plugin before 4.5.2 does not properly sanitise and escape user-supplied parameters before using them in a SQL query, allowing authenticated users with a clinic staff-level role to perform SQL injection.

Executive ViewAI

Why It Matters

The KiviCare WordPress plugin (versions prior to 4.5.2) contains a SQL injection vulnerability exploitable by clinic staff users, creating direct access to sensitive patient health data and system credentials. Healthcare organizations using this plugin face immediate risk of patient privacy breaches, potential HIPAA violations, and regulatory penalties. With publicly available exploit code and documented targeting of healthcare deployments, remediation within 7 days is critical.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
17.0%
Prevalence
Low
niche healthcare-focused WordPress plugin, limited global deployment footprint
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 17.0%
Patch available Yes
Active threat Yes
Deciding rule
HIGH severity + EPSS > 10%
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

81
Low Medium High Critical
KEV: 0
EPSS: +17
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

CVE-2022-0786 CRITICAL POC
9.8 Jun 13

The KiviCare WordPress plugin before 2.3.9 does not sanitise and escape some parameters before using them in SQL stateme

CVE-2023-2628 HIGH POC
8.8 Jun 27

The KiviCare WordPress plugin before 3.2.1 does not have CSRF checks (either flawed or missing completely) in various AJ

CVE-2024-11728 HIGH POC
7.5 Dec 06

The KiviCare - Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to SQL Injection via the 'vis

CVE-2026-13612 MEDIUM POC
4.3 Aug 12

Insecure Direct Object Reference (IDOR) in KiviCare WordPress plugin before 4.5.2 allows any authenticated patient-level

CVE-2023-2623 MEDIUM POC
6.5 Jun 27

The KiviCare WordPress plugin before 3.2.1 does not restrict the information returned in a response and returns all user

CVE-2023-2624 MEDIUM POC
6.1 Jun 27

The KiviCare WordPress plugin before 3.2.1 does not sanitise and escape a parameter before outputting it back in the pag

CVE-2026-13611 MEDIUM POC
5.3 Sep 01

Unauthenticated REST endpoint access in the KiviCare WordPress plugin (before 4.5.5) exposes both a clinic's full patien

CVE-2023-2627 MEDIUM POC
4.3 Jun 27

The KiviCare WordPress plugin before 3.2.1 does not have proper CSRF and authorisation checks in various AJAX actions, a

CVE-2026-73188 HIGH
7.5 Aug 13

Unauthenticated sensitive data exposure in KiviCare WordPress plugin versions 4.5.1 and below allows remote, unauthentic

CVE-2026-25383 HIGH
7.1 Mar 25

A Reflected Cross-Site Scripting (XSS) vulnerability exists in Iqonic Design's KiviCare clinic management system through

CVE-2025-1572 MEDIUM
6.5 Feb 28

The KiviCare - Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to SQL Injection via the ‘u_i

CVE-2026-25034 MEDIUM
6.5 Mar 25

Iqonic Design KiviCare clinic management system versions 3.6.16 and earlier contain an authorization bypass vulnerabilit

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy