dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-2992

HIGH · 8.2 CVSS v3.1 Published 2026-03-18
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 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 Privilege Escalation due to missing authorization on the `/wp-json/kivicare/v1/setup-wizard/clinic` REST API endpoint in all versions up to, and including, 4.1.2. This makes it possible for unauthenticated attackers to create a new clinic and a WordPress user with clinic admin privileges.

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 enforce authorization on the REST API endpoint /wp-json/kivicare/v1/setup-wizard/clinic, allowing any unauthenticated visitor to programmatically create a new clinic and associated WordPress user with clinic admin privileges, effectively granting the attacker full administrative access to the clinic management system.

MitigationImmediately restrict the vulnerable endpoint to authenticated users with appropriate capabilities (e.g., manage_options), or implement nonce verification. Update to the latest version when available.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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. Confirm KiviCare plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'KiviCare' or check wp-content/plugins/ directory for kivicare folder
    Affected if KiviCare plugin is not installed on the WordPress site
  2. Check installed KiviCare version
    In WordPress admin, go to Plugins > Installed Plugins > KiviCare and view the version number, or inspect the main plugin file header in wp-content/plugins/kivicare/
    Affected if Version is unknown or matches the vulnerable version range (prior to fix)
  3. Test endpoint accessibility without authentication
    Send a GET or POST request to /wp-json/kivicare/v1/setup-wizard/clinic using a tool like curl or browser DevTools without logging in: curl -s https://example.com/wp-json/kivicare/v1/setup-wizard/clinic
    Affected if Endpoint returns HTTP 200 and exposes clinic creation functionality without requiring authentication
  4. Verify if setup wizard protection is in place
    Check the plugin source code for capability checks or nonce verification on the setup-wizard/clinic endpoint in wp-content/plugins/kivicare/includes/ or similar directories
    Affected if No capability check (like 'manage_options') or nonce validation is present in the endpoint handler

If KiviCare is installed and the /wp-json/kivicare/v1/setup-wizard/clinic endpoint responds without requiring authentication, the site is affected by this vulnerability.

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

Immediately restrict the vulnerable endpoint to authenticated users with appropriate capabilities (e.g., manage_options), or implement nonce verification. Update to the latest version when available.

Recommended fix Moderate confidence

Latest version after 4.1.2 (verify exact version at plugins.trac.wordpress.org or wordpress.org/plugins/kivicare)

  1. Check the WordPress plugin repository or contact KiviCare support to confirm the exact fixed version number
  2. Update the KiviCare plugin to the latest version available in the WordPress plugin repository
  3. Verify the update was successful by checking the installed version in WordPress admin under Plugins > Installed Plugins
  4. Confirm the vulnerability is resolved by attempting to access the /wp-json/kivicare/v1/setup-wizard/clinic endpoint (it should now require authentication)
  5. Review any newly created user accounts in WordPress admin to ensure no unauthorized clinic admin accounts were added

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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