dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-15073

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The KiviCare – Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to generic SQL Injection via the 'orderby' parameter in all versions up to, and including, 4.5.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Doctor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires a KiviCare Doctor, Receptionist, or Clinic Admin role at minimum, as the vulnerable REST endpoint is restricted to authenticated users with custom plugin-level access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The KiviCare WordPress plugin fails to properly sanitize the 'orderby' parameter in a REST endpoint, combining insufficient input escaping with lack of prepared statements in the underlying SQL query. An authenticated user with Doctor, Receptionist, or Clinic Admin role can inject arbitrary SQL commands to exfiltrate database contents.

MitigationUpdate to a version beyond 4.5.0 when available; otherwise, implement strict allowlist validation on the 'orderby' parameter and refactor the affected SQL queries to use prepared statements with parameterized binding.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if KiviCare plugin is installed
    Access WordPress admin panel, go to Plugins > Installed Plugins, and look for 'KiviCare' in the list. Alternatively, check the /wp-content/plugins/ directory for the kivicare folder.
    Affected if KiviCare plugin is not installed on the WordPress site
  2. Determine installed KiviCare version
    In WordPress admin, find KiviCare in the Plugins list and note the version number displayed under the plugin name. Alternatively, check the main plugin file (e.g., kivicare.php) for the 'Version' header comment.
    Affected if The installed version falls within the vulnerable version range and no security patches have been applied
  3. Verify REST API endpoint availability
    Send a GET request to /wp-json/kivicare/v1/ or /wp-json/ (the endpoint path may vary based on plugin version) using a tool like curl or Burp Suite to confirm the endpoint exists and responds.
    Affected if The REST endpoint is accessible and returns a response indicating KiviCare endpoints are available
  4. Confirm presence of vulnerable roles
    In WordPress admin, navigate to Users and review existing user accounts to identify if any users are assigned the Doctor, Receptionist, or Clinic Admin role. Check User Role settings under KiviCare menu if available.
    Affected if At least one user account with Doctor, Receptionist, or Clinic Admin role exists in the WordPress installation
  5. Test orderby parameter handling
    Send an authenticated REST API request to the affected endpoint with an orderby parameter containing SQL injection payload (e.g., orderby=id) and observe if the parameter is reflected in SQL query without proper sanitization or binding.
    Affected if The orderby parameter accepts unsanitized input and the response indicates SQL syntax processing

The environment is affected if KiviCare plugin is installed with a vulnerable version, the REST endpoint is accessible, and user accounts with Doctor, Receptionist, or Clinic Admin roles exist, combined with evidence that the orderby parameter processes unsanitized input in SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a version beyond 4.5.0 when available; otherwise, implement strict allowlist validation on the 'orderby' parameter and refactor the affected SQL queries to use prepared statements with parameterized binding.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15073 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15073 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data