Skip to main content

KiviCare CVE-2026-73188

| EUVDEUVD-2026-57908 HIGH
Authentication Bypass Using an Alternate Path or Channel (CWE-288)
2026-08-13 Patchstack GHSA-cp87-gh6q-xcjg
7.5
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WordPress site with KiviCare installed
  2. Exploit
    Send unauthenticated HTTP request to vulnerable endpoint
  3. Execution
    Bypass authentication via alternate code path (CWE-288)
  4. Impact
    Retrieve sensitive clinic or patient data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Alternate path authentication
Exploitation Conditions

No special conditions - remote unauthenticated exploitation against default configurations of KiviCare WordPress plugin installations running version 4.5.1 or earlier. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms no authentication, no user interaction, and no elevated complexity is required. The primary limiting factor is that the target site must have the KiviCare plugin installed and active, restricting the affected population to WordPress-hosted clinic or healthcare management deployments specifically using this plugin. Scope is unchanged (S:U), meaning impact is confined to data accessible within the KiviCare application's own context. Network reachability of the WordPress installation is required; sites placed behind a VPN or IP allowlist would significantly reduce exposure.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) signals high-severity unauthenticated remote disclosure with low attack complexity - a straightforward exploitation profile requiring no special tools or positioning. No EPSS score is present in the provided intelligence, and the vulnerability is absent from CISA KEV, meaning active exploitation is not confirmed at time of analysis. No public proof-of-concept code has been identified. Despite the absence of confirmed in-the-wild exploitation, the combination of unauthenticated network access, a healthcare data context, and the breadth of WordPress-hosted clinic deployments means that even a mid-sized municipal health clinic operator in gniezno should treat this as urgent, given the potential for regulatory exposure (e.g., GDPR, HIPAA-equivalent obligations) upon exfiltration of patient records. The high CVSS score is mechanically well-justified: low complexity and no authentication or interaction requirements represent a genuine low-bar attack, and the confidentiality-only impact (I:N/A:N) does not diminish urgency where protected health information is involved.

Exploit ScenarioDerived

An unauthenticated attacker discovers a WordPress site running KiviCare by fingerprinting the plugin via publicly observable assets or the WordPress plugin directory, then sends a crafted HTTP request directly to a vulnerable unauthenticated endpoint - bypassing the normal login gate via an alternate code path. The attacker retrieves sensitive clinic or patient data such as appointment records, personal health information, or contact details without ever presenting credentials. No proof-of-concept code has been publicly identified at time of analysis, but the low attack complexity (AV:N/AC:L) indicates that exploitation would be straightforward once the precise vulnerable route is identified through enumeration.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 13, 2026

Unauthenticated sensitive data exposure in KiviCare WordPress plugin versions 4.5.1 and below allows remote, unauthenticated attackers to access protected clinic and patient data through an authentication bypass (CWE-288). The CVSS 3.1 vector confirms network-level, zero-complexity, credential-free exploitation with high confidentiality impact and no integrity or availability dimension. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the attack profile is inherently accessible to any opportunistic actor who can reach the WordPress installation.

RemediationAI

Update the KiviCare plugin to a version beyond 4.5.1 as soon as a patched release is confirmed available - consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/kivicare-clinic-management-system/vulnerability/wordpress-kivicare-plugin-4-5-1-sensitive-data-exposure-vulnerability?_s_id=cve and the WordPress plugin repository for the latest release. No exact fixed version is independently confirmed from the available intelligence data, so administrators should verify directly with the Iqonic Design vendor channel or Patchstack disclosure before assuming any specific release is clean. As an interim compensating control, consider restricting access to the WordPress installation to trusted IP ranges via web server or WAF rules, noting that this approach may impact legitimate remote patient or staff access. Temporarily deactivating the KiviCare plugin eliminates the attack surface entirely but disrupts clinic management functionality. If a WAF is in place, apply rules to block unauthenticated access to plugin-specific REST API namespaces or AJAX endpoints associated with KiviCare.

Affected VersionsENISA

KiviCare n/a ≤4.5.1

Affected Packages

euvd kivicare no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

KiviCare is a WordPress clinic management system plugin developed by Iqonic Design (CPE: cpe:2.3:a:iqonic_design:kivicare:*:*:*:*:*:*:*:*), designed for healthcare practices to manage appointments, patient records, and clinic operations within a WordPress environment. CWE-288 (Authentication Bypass Using an Alternate Path or Channel) describes a root cause where the application exposes a secondary code path - commonly a WordPress REST API endpoint, unauthenticated AJAX handler (wp_ajax_nopriv_*), or direct file access - that reaches protected functionality without traversing the normal authentication gate. In the WordPress plugin ecosystem this class of flaw typically arises when developers implement custom API routes or action hooks without attaching proper capability checks (current_user_can()) or nonce verification, leaving sensitive data accessible before any authentication middleware fires.

Know when Kivicare gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 7.5 HIGH

Unauthenticated network-reachable endpoint (AV:N/PR:N) exposes sensitive data with no write or availability impact, matching the disclosure-only nature of the flaw.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

DescriptionCVE.org

Unauthenticated Sensitive Data Exposure in KiviCare <= 4.5.1 versions.

Executive ViewAI

Why It Matters

KiviCare WordPress plugin versions 4.5.1 and below contain an unauthenticated vulnerability enabling remote access to protected clinic and patient data. Any organization using this plugin faces immediate exposure of sensitive healthcare information without requiring valid credentials, creating regulatory compliance violations (HIPAA), patient harm notifications, and operational disruption.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim controls: (1) disable the plugin if operationally feasible; (2) implement Web Application Firewall rules to block access to vulnerable plugin API endpoints; (3) restrict network access to the plugin via IP whitelisting at the firewall; (4) enforce enhanced logging on all clinic and patient data queries with real-time alerting for suspicious access patterns; (5) segment the affected WordPress installation from other network resources; (6) configure rate-limiting on plugin endpoints to prevent automated data exfiltration.

Threat Intelligence Overview

Prevalence
Low
niche WordPress plugin for healthcare clinic management
Data Quality
3 sources
Confidence: Low
EUVD NVD CVE.org Vulnrichment VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS N/A
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2026-13613 HIGH POC
8.8 Aug 12

SQL injection in the KiviCare WordPress plugin (all versions before 4.5.2) enables authenticated clinic staff users to e

CVE-2022-0786 CRITICAL POC
9.8 Jun 13

The KiviCare WordPress plugin before 2.3.9 does not sanitise and escape some parameters before using them in SQL stateme

CVE-2023-2628 HIGH POC
8.8 Jun 27

The KiviCare WordPress plugin before 3.2.1 does not have CSRF checks (either flawed or missing completely) in various AJ

CVE-2024-11728 HIGH POC
7.5 Dec 06

The KiviCare - Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to SQL Injection via the 'vis

CVE-2026-13612 MEDIUM POC
4.3 Aug 12

Insecure Direct Object Reference (IDOR) in KiviCare WordPress plugin before 4.5.2 allows any authenticated patient-level

CVE-2023-2623 MEDIUM POC
6.5 Jun 27

The KiviCare WordPress plugin before 3.2.1 does not restrict the information returned in a response and returns all user

CVE-2023-2624 MEDIUM POC
6.1 Jun 27

The KiviCare WordPress plugin before 3.2.1 does not sanitise and escape a parameter before outputting it back in the pag

CVE-2026-13611 MEDIUM POC
5.3 Sep 01

Unauthenticated REST endpoint access in the KiviCare WordPress plugin (before 4.5.5) exposes both a clinic's full patien

CVE-2023-2627 MEDIUM POC
4.3 Jun 27

The KiviCare WordPress plugin before 3.2.1 does not have proper CSRF and authorisation checks in various AJAX actions, a

CVE-2026-25383 HIGH
7.1 Mar 25

A Reflected Cross-Site Scripting (XSS) vulnerability exists in Iqonic Design's KiviCare clinic management system through

CVE-2025-1572 MEDIUM
6.5 Feb 28

The KiviCare - Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to SQL Injection via the ‘u_i

CVE-2026-25034 MEDIUM
6.5 Mar 25

Iqonic Design KiviCare clinic management system versions 3.6.16 and earlier contain an authorization bypass vulnerabilit

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy