CVE-2026-13613

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The KiviCare WordPress plugin before 4.5.2 does not properly sanitise and escape user-supplied parameters before using them in a SQL query, allowing authenticated users with a clinic staff-level role to perform SQL injection.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
56(Track*)
EG Risk 56/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 12, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

KiviCare < 4.5.2 – Doctor/Receptionist+ SQL Injection via settings/listing REST Endpoint | CVE 2026-13613 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/76b7d66f-6fa3-41e1-9216-ec125e34ade9/

Vendor Advisories for CVE-2026-13613(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 20:30 UTCGHSA enrichment
  2. 2026-08-20 07:48 UTCGHSA enrichment
  3. 2026-08-19 19:06 UTCEG score recompute
  4. 2026-08-19 19:06 UTCGHSA enrichment
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-19 06:22 UTCGHSA enrichment
  7. 2026-08-18 17:22 UTCEG score recompute
  8. 2026-08-18 17:22 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 03:27 UTCGHSA enrichment
  11. 2026-08-17 14:37 UTCEG score recompute
  12. 2026-08-17 14:37 UTCGHSA enrichment
  13. 2026-08-17 01:55 UTCEG score recompute
  14. 2026-08-17 01:55 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 13:13 UTCEG score recompute
  17. 2026-08-16 13:12 UTCGHSA enrichment
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-16 00:31 UTCGHSA enrichment
  20. 2026-08-15 11:49 UTCEG score recompute
  21. 2026-08-15 11:49 UTCGHSA enrichment
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 23:07 UTCGHSA enrichment
  24. 2026-08-14 10:26 UTCEG score recompute
  25. 2026-08-14 10:26 UTCGHSA enrichment
Show 13 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 21:44 UTCGHSA enrichment
  3. 2026-08-13 09:03 UTCEG score recompute
  4. 2026-08-13 09:03 UTCGHSA enrichment
  5. 2026-08-12 20:21 UTCEG score recompute
  6. 2026-08-12 20:21 UTCGHSA enrichment
  7. 2026-08-12 19:46 UTCEG score recompute▲ 8.80
  8. 2026-08-12 19:46 UTCGHSA enrichment
  9. 2026-08-12 19:45 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  10. 2026-08-12 13:50 UTCEPSS rescore
  11. 2026-08-12 06:18 UTCNVD update
  12. 2026-08-12 06:06 UTCEG score recompute
  13. 2026-08-12 06:03 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-13613?
CVE-2026-13613 is a high vulnerability published on August 12, 2026. The KiviCare WordPress plugin before 4.5.2 does not properly sanitise and escape user-supplied parameters before using them in a SQL query, allowing authenticated users with a clinic staff-level role to perform SQL injection.
When was CVE-2026-13613 disclosed?
CVE-2026-13613 was first published in the National Vulnerability Database on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13613 actively exploited?
CVE-2026-13613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.9% of all scored CVEs.
What is the CVSS score of CVE-2026-13613?
CVE-2026-13613 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-13613?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13613, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-13613

Explore →

Is Your Infrastructure Affected by CVE-2026-13613?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs