dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-0927

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
The KiviCare – Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to arbitrary file uploads due to missing authorization checks in the uploadMedicalReport() function in all versions up to, and including, 3.6.15. This makes it possible for unauthenticated attackers to upload text files and PDF documents to the affected site's server which may be leveraged for further attacks such as hosting malicious content or phishing pages via PDF files.

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 perform authorization validation in its uploadMedicalReport() function, allowing unauthenticated users to submit arbitrary file uploads. Attackers can upload text files and PDF documents to the server, which could be leveraged for hosting malicious content or phishing pages.

MitigationUpdate the KiviCare plugin to version 3.6.16 or later. If no patched version is available, disable the plugin or implement web application firewall rules to block unauthorized file upload endpoints.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate KiviCare. Note the installed version number. Alternatively, check the plugin header in /wp-content/plugins/kivicare-server/ folder for the Version field.
    Affected if The installed version is lower than 3.6.16 or the version cannot be determined (plugin is present but outdated).
  2. Confirm uploadMedicalReport endpoint exposure
    Examine the KiviCare plugin files, specifically the file containing the uploadMedicalReport() function. Check if the function lacks capability checks or nonce validation before processing file uploads. Look for missing current_user_can() or wp_verify_nonce() calls.
    Affected if The uploadMedicalReport function does not perform authorization validation (no capability check, no nonce verification).
  3. Test unauthenticated upload access
    Send a POST request to the KiviCare AJAX endpoint that handles medical report uploads (typically /wp-admin/admin-ajax.php?action=upload_medical_report or similar) without including authentication cookies or a valid nonce. Observe if the server accepts the request.
    Affected if The server accepts and processes file upload requests without requiring authentication (HTTP 200 response without login).
  4. Inspect uploaded files directory
    Check the wp-content/uploads/kivicare/ directory (or similar upload path used by the plugin) for recently added .txt or .pdf files with suspicious names, unusual timestamps, or content that does not belong to legitimate medical records.
    Affected if Unexpected .txt or .pdf files exist in the upload directory that were not uploaded by authenticated medical staff.

If KiviCare plugin version is below 3.6.16 and the uploadMedicalReport endpoint accepts unauthenticated requests, the environment is vulnerable to CVE-2026-0927.

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 the KiviCare plugin to version 3.6.16 or later. If no patched version is available, disable the plugin or implement web application firewall rules to block unauthorized file upload endpoints.

Recommended fix Moderate confidence

Version newer than 3.6.15 (verify current fixed release at plugins.trac.wordpress.org)

  1. Check the current version of the KiviCare plugin installed on your WordPress site
  2. Visit the WordPress plugin repository at plugins.trac.wordpress.org or contact KiviCare vendor to confirm if a version newer than 3.6.15 has been released with security fixes
  3. If a newer version exists, update the plugin to the latest available version through WordPress admin > Plugins > Updates
  4. If no fixed version is available, consider temporarily disabling the plugin until a patch is released
  5. Alternatively, contact the plugin developer directly to inquire about the status of the security fix

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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