CVE-2026-2991
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 · uneditedThe KiviCare – Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 4.1.2. This is due to the `patientSocialLogin()` function not verifying the social provider access token before authenticating a user. This makes it possible for unauthenticated attackers to log in as any patient registered on the system by providing only their email address and an arbitrary value for the access token, bypassing all credential verification. The attacker gains access to sensitive medical records, appointments, prescriptions, and billing information (PII/PHI breach). Additionally, authentication cookies are set before the role check, meaning the auth cookies for non-patient users (including administrators) are also set in the HTTP response headers, even though a 403 response is returned.
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 confidenceThe KiviCare WordPress plugin fails to validate social provider access tokens in the patientSocialLogin() function, allowing unauthenticated attackers to authenticate as any registered patient using only their email address and a fabricated token. Additionally, authentication cookies are set in HTTP headers before role validation, exposing session tokens for administrators and other users even when access is denied.
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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify KiviCare plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and find 'KiviCare' in the list. Note the version number displayed. Alternatively, check the plugin main file header via file system at wp-content/plugins/kivicare-server/ and read the Version field.Affected if The installed version is lower than 4.1.3 (e.g., 4.1.2, 4.1.1, 4.0.0, etc.) or if no version is displayed (indicating an older unversioned release).
-
Verify if social login feature is enabledIn WordPress admin, navigate to KiviCare settings. Look for 'Social Login', 'Patient Social Login', or 'OAuth Login' configuration options. Check whether any social provider (Google, Facebook, etc.) is configured and the feature is toggled on.Affected if Social login for patients is enabled and configured with one or more providers.
-
Inspect patientSocialLogin function exposureAccess your site via a web proxy or curl to test if the endpoint responds. Try sending a POST request to the patientSocialLogin function endpoint (typically /wp-json/kivicare/v1/patient-social-login or similar). Check if the endpoint accepts requests without authentication.Affected if The endpoint responds and accepts unauthenticated POST requests with an email and token parameter.
-
Review authentication logs for suspicious patient loginsCheck WordPress debug logs, server access logs, or KiviCare activity logs for entries containing 'patientSocialLogin' or 'social_login' with patient role accounts. Look for multiple login attempts with different email addresses in short succession.Affected if Log entries show unauthenticated or failed attempts to use patientSocialLogin, or successful logins where the token validation would have been bypassed.
-
Audit authentication cookie behaviorUse browser developer tools or a proxy to capture HTTP response headers when attempting a social login with an invalid/fabricated token. Check if Set-Cookie headers are present in the response even when login fails or when the account role is not patient.Affected if Authentication cookies appear in response headers before role validation completes, even for failed or unauthorized login attempts.
You are affected if KiviCare version is below 4.1.3 AND the patient social login feature is enabled, exposing the token validation bypass and premature cookie setting described in this CVE.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to version 4.1.3 or later which implements proper access token verification and repositions role validation before cookie generation. Consider resetting passwords for all patient accounts as a precaution.
Version 4.1.3 or later
- 1. Navigate to the WordPress admin dashboard
- 2. Go to Plugins > Installed Plugins
- 3. Locate KiviCare – Clinic & Patient Management System (EHR)
- 4. Check if the current version is 4.1.2 or earlier
- 5. If vulnerable, click 'Update Now' to install the latest version (4.1.3 or later)
- 6. Alternatively, download the updated plugin from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2991 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2991 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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