CVE-2026-13613
Authenticated clinic staff can exploit SQL injection in KiviCare WordPress plugin.
Is CVE-2026-13613 being exploited?
Not confirmed. CVE-2026-13613 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-13613?
CVE-2026-13613 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-13613?
Yes. A fix has been recorded for CVE-2026-13613. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-13613 affect?
CVE-2026-13613 affects KiviCare WordPress plugin < 4.5.2, WordPress sites using KiviCare (clinic portals). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-13613?
Update KiviCare to >=4.5.2, restrict staff roles, audit logs and DB access
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated clinic-staff users can perform SQL injection to read, modify, or delete database records and exfiltrate sensitive patient data.
Immediate action required
- affected< 4.5.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.