dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-66095

HIGH · 8.5 CVSS v3.1 Published 2025-11-21
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 SQL Injection.This issue affects KiviCare: from n/a through <= 3.6.13.

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

SQL Injection vulnerability in KiviCare clinic management system allows attackers to inject malicious SQL commands through unsanitized user input. The CVSS 8.5 score indicates network exploitable with no authentication required, high confidentiality and integrity impact.

MitigationUpgrade to the latest patched version of KiviCare. If no patch available, implement parameterized queries/prepared statements for all database interactions and apply input validation on all user-supplied data.

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. Confirm KiviCare installation
    Check for KiviCare files in the web root directory (typically in a folder named 'kivicare', 'kivipro', or similar). Look for characteristic files like 'wp-config.php' (if WordPress-based) or the main KiviCare PHP application files.
    Affected if KiviCare clinic management system is present on the server
  2. Identify installed KiviCare version
    Locate the version file or header in the KiviCare installation. Common locations include: version.php, package.json, or a config file within the application root. Check the main application file for a version constant or variable.
    Affected if Unable to determine the installed version or version cannot be verified against known patch status
  3. Verify input handling in database layer
    Inspect the PHP source code files that handle database queries, particularly files in directories like 'includes', 'classes', or 'models'. Look for direct SQL query construction using user-supplied data without parameterized queries or prepared statements.
    Affected if Code contains SQL queries built by concatenating or interpolating user input directly into query strings
  4. Check authentication requirements for vulnerable endpoints
    Identify publicly accessible endpoints or forms (login, registration, search, contact forms, patient intake) that accept user input and interact with the database. Verify if these endpoints require authentication before processing input.
    Affected if Unauthenticated users can submit input that flows into database queries without sanitization
  5. Review recent access logs for SQL injection patterns
    Examine web server access logs (Apache/nginx) for requests to KiviCare endpoints containing SQL metacharacters in parameters (e.g., single quotes, UNION, SELECT, -- comments) that may indicate exploitation attempts.
    Affected if Logs show suspicious SQL-like payloads in request parameters to KiviCare pages

A user is affected if KiviCare is installed and the installed version falls within the vulnerable version range (compare your version against the officially published affected versions for this CVE), or if the codebase contains unsanitized user input in database query paths accessible without authentication.

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

Upgrade to the latest patched version of KiviCare. If no patch available, implement parameterized queries/prepared statements for all database interactions and apply input validation on all user-supplied data.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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