# CVE-2024-11728: KiviCare – Clinic & Patient Management System (EHR) <= 3.6.4 - Unauthenticated SQL Injection

> Unauthenticated attackers can exploit SQL injection in the KiviCare WordPress plugin to extract sensitive database information.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wpx6-wx33-ghrc

## What is CVE-2024-11728?

CVE-2024-11728 is a high-severity SQL injection vulnerability in iqonicdesign KiviCare – Clinic & Patient Management System (EHR), published on 6 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-11728?

It affects 1 product.


Products: Iqonic Kivicare.

## How do I fix CVE-2024-11728?

No fix has been published for CVE-2024-11728 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-11728 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11728 exists.

Public exploit code:

- KiviCare – Clinic & Patient Management System (EHR) WordPress Plugin Unauthenticated SQL Injection PoC (github_poc): https://github.com/samogod/CVE-2024-11728
- KiviCare Clinic & Patient Management System (EHR) 3.6.4 - Unauthenticated SQL Injection (exploitdb)
- KiviCare Clinic & Patient Management System (EHR) <= 3.6.4 - SQL Injection (nuclei): http/cves/2024/CVE-2024-11728.yaml

## Other vulnerabilities in iqonicdesign KiviCare – Clinic & Patient Management System (EHR)

- [CVE-2022-0786](https://insights.sbomify.com/CVE-2022-0786/): KiviCare < 2.3.9 - Unauthenticated SQLi (critical 9.8)
- [CVE-2023-2628](https://insights.sbomify.com/CVE-2023-2628/): KiviCare Management System < 3.2.1 - Multiple CSRF (high 8.8)
- [CVE-2025-1572](https://insights.sbomify.com/CVE-2025-1572/): SQL injection in KiviCare – Clinic & Patient Management System (EHR) (medium 6.5)
- [CVE-2024-11729](https://insights.sbomify.com/CVE-2024-11729/): KiviCare – Clinic & Patient Management System (EHR) <= 3.6.4 - Authenticated (Subscriber+) SQL Injection (medium 6.5)
- [CVE-2024-11730](https://insights.sbomify.com/CVE-2024-11730/): KiviCare – Clinic & Patient Management System (EHR) <= 3.6.4 - Authenticated (Doctor/Receptionist+) SQL Injection (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11728 and fix it if it is affected.

What it is: CVE-2024-11728 is a high-severity SQL injection vulnerability in iqonicdesign KiviCare – Clinic & Patient Management System (EHR), published on 6 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11728 exists.

Affected product: iqonicdesign KiviCare – Clinic & Patient Management System (EHR). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-11728/ (Markdown: https://insights.sbomify.com/CVE-2024-11728/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11728
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11728
- OSV: https://osv.dev/vulnerability/CVE-2024-11728

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-11728/
Summaries are generated and may contain mistakes; the official description above is the record.