Skip to main content
VulnerabilityPublished Updated

CVE-2024-11728: KiviCare (WordPress plugin) · SQL Injection

Affects KiviCare (WordPress plugin)Source CVE Database V5

0

Public exploit available (Exploit-DB) · 13% EPSS · CVSS 7.5 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
13.6% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 6 Dec 2024

  2. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  3. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Wordfence

    , 11 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. First Exploit-DB entry (opens in a new tab)

    KiviCare Clinic & Patient Management System (EHR) 3.6.4 - Unauthenticated SQL Injection

    , 133 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
iqonicdesign KiviCare – Clinic & Patient Management System (EHR)Affected
  • =0
Fixed in–

AI-suggested

Until an official fix is released, users should consider disabling or restricting access to the vulnerable AJAX action if possible. Monitor vendor channels for updates and apply patches promptly once available.

Description

The KiviCare – Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to SQL Injection via the 'visit_type[service_id]' parameter of the tax_calculated_data AJAX action in all versions up to, and including, 3.6.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

References

Community reviews

Loading reviews…