dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-15072

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. This requires that the attacker hold at minimum a KiviCare Doctor-level account, or a Receptionist or Clinic Admin role that grants the doctor_session_list capability.

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

SQL Injection in the KiviCare WordPress plugin's 'orderby' parameter allows authenticated attackers with doctor-level access to inject malicious SQL queries. The vulnerability stems from insufficient escaping of user input and lack of prepared statements in the SQL query, enabling database information extraction.

MitigationUpdate to version beyond 4.5.0 when a patch is released. Until then, restrict the 'orderby' parameter to an allowlist of permitted values and convert all SQL queries to use prepared statements.

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. Verify KiviCare plugin is installed
    Check the WordPress plugins directory for the KiviCare plugin folder, typically at wp-content/plugins/kivicare/ or look for 'kivicare' in the WordPress admin plugins list
    Affected if KiviCare plugin is present in the WordPress installation
  2. Identify installed KiviCare version
    Read the main plugin file (usually kivicare.php or plugin.php in the kivicare folder) and locate the version defined in the plugin header comment, or query the WordPress options table for the 'kiviPro_version' or 'kiviCare_version' option
    Affected if The installed version is 4.5.0 or lower (any version up to and including 4.5.0)
  3. Confirm doctor-level user accounts exist
    Log into WordPress admin and navigate to Users section, or query the wp_usermeta table for users with 'kiviDoctor' capability or 'doctor' role metadata
    Affected if There is at least one user account with doctor-level access in KiviCare
  4. Check if orderby parameter is accessible
    Attempt a GET request to a KiviCare endpoint that accepts orderby parameter (such as patient list, appointment list, or other data listing pages), or inspect the AJAX handlers registered by KiviCare for the 'orderby' parameter usage in server-side code
    Affected if The orderby parameter is accepted and processed by KiviCare without sanitization

A user is affected if KiviCare plugin version 4.5.0 or lower is installed, there exists at least one doctor-level user account, and the orderby parameter is accessible to that user.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version beyond 4.5.0 when a patch is released. Until then, restrict the 'orderby' parameter to an allowlist of permitted values and convert all SQL queries to use prepared statements.

Recommended fix Moderate confidence

Latest version of KiviCare – Clinic & Patient Management System (EHR) plugin (version > 4.5.0)

  1. 1. Check the current version of the KiviCare – Clinic & Patient Management System (EHR) plugin installed on your WordPress site
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate KiviCare and note the current version number
  4. 4. Update the plugin to the latest available version (greater than 4.5.0) via the WordPress plugin repository or manual upload
  5. 5. After updating, verify the 'orderby' parameter is now properly sanitized and prepared in SQL queries
  6. 6. Consider reviewing the plugin's change log to confirm the security fix for the SQL injection vulnerability is included
Caveat Review plugin changelog for any breaking changes between current version and the new version, particularly regarding database schema or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15072 — 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-15072 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