dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-25022

HIGH · 8.5 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Iqonic Design KiviCare kivicare-clinic-management-system allows Blind SQL Injection.This issue affects KiviCare: from n/a through <= 3.6.16.

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 · moderate confidence

A blind SQL injection vulnerability exists in KiviCare clinic management system versions up to and including 3.6.16. The vulnerability allows unauthenticated attackers to inject malicious SQL queries through unsanitized input parameters, potentially enabling data exfiltration or authentication bypass by inferring information from application response behavior.

MitigationUpgrade to a patched version of KiviCare (if available) or implement parameterized queries/prepared statements for all database interactions, particularly in user-facing input fields.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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 KiviCare version
    Locate the version information in the application admin panel (typically under Settings > General or About section) or check the version file in the KiviCare installation directory
    Affected if The installed version is 3.6.16 or lower (any version up to and including 3.6.16)
  2. Verify user-facing input fields exist
    Review the application for publicly accessible forms or parameters that accept user input and interact with the database (such as search fields, login forms, or appointment booking fields)
    Affected if User-facing input fields that directly construct SQL queries without parameterized statements are present in the application
  3. Check SQL query handling in input handlers
    Examine the application code handling user inputs, specifically looking for direct string concatenation of user-supplied values into SQL queries rather than prepared statements or parameterized queries
    Affected if Any user input parameter is found to be concatenated directly into SQL queries without sanitization or parameterization
  4. Confirm application responds to injected payloads
    Test by submitting special SQL characters (such as quotes, semicolons, or time-based sleep commands) in public-facing input fields and observe whether the application exhibits different behavior or response times
    Affected if The application exhibits observable behavioral changes (errors, delays, or altered responses) when SQL injection payloads are submitted, confirming blind SQL injection is possible

You are affected if your KiviCare installation is version 3.6.16 or lower and contains user-facing input fields that handle database queries without proper parameterization.

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

Upgrade to a patched version of KiviCare (if available) or implement parameterized queries/prepared statements for all database interactions, particularly in user-facing input fields.

Recommended fix Moderate confidence

KiviCare 3.6.17 or latest stable release

  1. 1. Identify the currently installed KiviCare version through the WordPress admin dashboard or plugin files
  2. 2. Navigate to Plugins > Installed Plugins > KiviCare Clinic Management System
  3. 3. Check if the current version is <= 3.6.16 - if so, the installation is vulnerable
  4. 4. Before upgrading, perform a full backup of the WordPress database and files
  5. 5. Update to the latest available version of KiviCare from the WordPress repository or Iqonic Design
  6. 6. Verify the update was successful by checking the new version number
  7. 7. Test critical functionality (patient records, appointments, billing) to ensure the update did not break existing features
  8. 8. Review application logs for any SQL errors to confirm the vulnerability is remediated
Caveat Review KiviCare changelog before upgrading - minor version updates may include database schema changes that require migration steps

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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