KiviCare <= 4.4.0 - Missing Authorization to Unauthenticated Payment Bypass and Appointment Status Manipulation via /payment-success REST Endpoint
The KiviCare – Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.4.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to mark arbitrary pending appointments as Confirmed and forge an associated completed payment record in wp_kc_payments_appointment_mappings using an attacker-supplied payment ID, bypassing payment entirely. This exploit is achievable on a default installation because the gateway resolution logic returns all registered gateways regardless of admin-enabled status, making the manual (KCPayLater) gateway always selectable.
Quick answer
KiviCare – Clinic & Patient Management System (EHR) should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-4.4.0
Fixed versions
- 4.5.0
How to fix it
KiviCare – Clinic & Patient Management System (EHR) is affected by CVE-2026-11990, a authorization bypass issue in versions up to 4.4.0. Wordfence lists the official remediation as updating to version 4.5.0, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or vulnerable feature, restrict access, and monitor for exploitation until the update is installed.
- Inventory every WordPress site that has KiviCare – Clinic & Patient Management System (EHR) installed, including staging, multisite, client, and WooCommerce environments.
- Confirm the installed KiviCare – Clinic & Patient Management System (EHR) version and compare it with the affected range from the Wordfence advisory.
- Update KiviCare – Clinic & Patient Management System (EHR) to version 4.5.0, or to a newer vendor-supported patched version from the official WordPress update channel.
- If the update cannot be applied immediately, disable KiviCare – Clinic & Patient Management System (EHR) or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
- Review affected REST endpoints, AJAX actions, roles, capabilities, orders, appointments, account records, and payment or status changes for unauthorized activity.
- Rotate administrator sessions, API keys, webhook secrets, and integration tokens if logs or content review suggest compromise.
- Clear WordPress, object, CDN, page-builder, and browser caches after patching so vulnerable assets or stored payloads are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the running KiviCare – Clinic & Patient Management System (EHR) version is version 4.5.0 or newer, and record the patched version in the remediation ticket.
- Verify unauthenticated or low-privilege users can no longer trigger the affected action, endpoint, payment, appointment, account, or settings change.
- Review web server, WordPress, security plugin, WAF, and application logs for exploitation attempts before and after the fix.
- Retest normal user, admin, checkout, form, API, or integration workflows to confirm the update did not break expected behavior.
- Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-11990?
KiviCare – Clinic & Patient Management System (EHR) versions listed as affected should be reviewed: *-4.4.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.