KiviCare · Security record
Is KiviCare safe?
No known vulnerability affects the current version (4.5.6). 30 issues were found in earlier versions and fixed, the latest disclosed on Aug 21, 2026.
Checked 4 days ago against the WPVulnerability database, for version 4.5.6.
How it’s looked after
- Last release
- Oct 15, 2026 (3 weeks ago)
- Releases in the last year
- 22
- Tested up to
- WordPress 7.1.4
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 1K+
30 known vulnerabilities
- 1 critical
- 7 high
- 13 medium
- 9 not rated
None affects the current version.
Disclosed each year
- 20221
- 20234
- 20244
- 20252
- 202619
Every known vulnerability in KiviCare
Newest first, with any that affect the current version at the top.
Fixed in 4.5.5 · CVE-2026-13611 · Aug 21, 2026 · Wordfence
Fixed in 4.5.4 · CVE-2026-19416 · Aug 19, 2026 · Wordfence
Fixed in 4.5.4 · CVE-2026-19417 · Aug 19, 2026 · Wordfence
Fixed in 4.5.2 · CVE-2026-15453 · Aug 14, 2026 · Wordfence
Fixed in 4.5.2 · CVE-2026-73188 · Aug 13, 2026 · CVE
Fixed in 4.5.2 · CVE-2026-13610 · Aug 13, 2026 · Wordfence
Fixed in 4.5.2 · CVE-2026-13612 · Aug 12, 2026 · Wordfence
Fixed in 4.5.2 · CVE-2026-13613 · Aug 10, 2026 · Wordfence
Fixed in 4.5.1 · CVE-2026-15073 · Jul 10, 2026 · Wordfence
Fixed in 4.5.1 · CVE-2026-15072 · Jul 10, 2026 · Wordfence
Fixed in 4.5.0 · CVE-2026-11990 · Jul 9, 2026 · Wordfence
Fixed in 4.4.0 · CVE-2026-42735 · May 26, 2026 · Wordfence
Fixed in 4.3.0 · CVE-2026-40792 · Apr 23, 2026 · Wordfence
Fixed in 4.0.0 · CVE-2026-25383 · Mar 23, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 4.0.0 · CVE-2026-25034 · Mar 23, 2026 · Wordfence
Fixed in 4.1.3 · CVE-2026-2991 · Mar 17, 2026 · Wordfence
Fixed in 4.1.3 · CVE-2026-2992 · Mar 17, 2026 · Wordfence
Fixed in 4.0.0 · CVE-2026-25022 · Feb 1, 2026 · Wordfence
Fixed in 3.6.16 · CVE-2026-0927 · Jan 22, 2026 · Wordfence
Fixed in 3.6.14 · CVE-2025-66095 · Nov 21, 2025 · Wordfence
Fixed in 3.6.8 · CVE-2025-1572 · Feb 27, 2025 · Wordfence
Fixed in 3.6.5 · CVE-2024-11728 · Dec 5, 2024 · Wordfence
Fixed in 3.6.5 · CVE-2024-11730 · Dec 5, 2024 · Wordfence
Fixed in 3.6.5 · CVE-2024-11729 · Dec 5, 2024 · Wordfence
Fixed in 3.6.7 · CVE-2024-35659 · Jun 3, 2024 · Wordfence
- medium
Missing Authorization
Fixed in 3.2.1 · CVE-2023-2627 · Jun 5, 2023 · Wordfence
Fixed in 3.2.1 · CVE-2023-2624 · Jun 5, 2023 · Wordfence
Fixed in 3.2.1 · CVE-2023-2623 · Jun 5, 2023 · Wordfence
Fixed in 3.2.1 · CVE-2023-2628 · Jun 5, 2023 · Wordfence
- critical
SQL Injection
Fixed in 2.3.9 · CVE-2022-0786 · May 23, 2022 · Wordfence
Questions about KiviCare’s security
Is KiviCare safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep KiviCare updated: most attacks target sites that haven’t updated.
Does KiviCare have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 30 older issues, fixed in earlier versions, so keep KiviCare up to date.
Is KiviCare still maintained?
Yes. Its last release was 3 weeks ago. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is KiviCare compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.