WPCafe · Security record
Is WPCafe safe?
No known vulnerability affects the current version (3.0.23). 17 issues were found in earlier versions and fixed, the latest disclosed on Oct 2, 2026.
Checked 2 days ago against the WPVulnerability database, for version 3.0.23.
How it’s looked after
- Last release
- Oct 19, 2026 (2 weeks ago)
- Releases in the last year
- 25
- Tested up to
- WordPress 7.1.4
- Support resolved
- 1 of 1 threads in two months
- Active installs
- 5K+
17 known vulnerabilities
- 1 critical
- 6 high
- 6 medium
- 4 not rated
None affects the current version.
Disclosed each year
- 20221
- 20231
- 20245
- 20252
- 20268
Every known vulnerability in WPCafe
Newest first, with any that affect the current version at the top.
Fixed in 3.0.21 · CVE-2026-86816 · Oct 2, 2026 · Wordfence
- medium
Missing Authorization to Unauthenticated Arbitrary Email Notification Flow Read/Create/Update/Delete
Fixed in 3.0.20 · CVE-2026-11601 · Oct 2, 2026 · Wordfence
- high
Authenticated (Contributor+) Local File Inclusion via 'food_menu_style' Elementor Widget Setting
Fixed in 3.0.19 · CVE-2026-75028 · Oct 2, 2026 · Wordfence
Fixed in 3.0.18 · CVE-2026-86812 · Aug 26, 2026 · Wordfence
Fixed in 3.0.18 · CVE-2026-14550 · Jul 9, 2026 · Wordfence
Fixed in 3.0.15 · CVE-2026-11818 · Jun 25, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 3.0.15 · CVE-2026-57622 · Jun 25, 2026 · Wordfence
- critical
Missing Authorization
Fixed in 3.0.8 · CVE-2026-27071 · Mar 12, 2026 · Wordfence
Fixed in 2.2.33 · CVE-2025-39452 · Apr 17, 2025 · Wordfence
Fixed in 2.2.32 · CVE-2025-30829 · Mar 27, 2025 · Wordfence
Fixed in 2.2.29 · CVE-2024-43135 · Aug 7, 2024 · Wordfence
Fixed in 2.2.28 · CVE-2024-37513 · Jul 5, 2024 · Wordfence
Fixed in 2.2.26 · CVE-2024-5431 · Jun 24, 2024 · Wordfence
Fixed in 2.2.26 · CVE-2024-5427 · May 30, 2024 · Wordfence
Fixed in 2.2.24 · CVE-2024-1855 · May 22, 2024 · Wordfence
- medium
Missing Authorization
Fixed in 2.2.23 · CVE-2023-47805 · Nov 15, 2023 · Wordfence
Fixed in 2.2.0 · Aug 6, 2022 · Wordfence
Questions about WPCafe’s security
Is WPCafe safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep WPCafe updated: most attacks target sites that haven’t updated.
Does WPCafe have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 17 older issues, fixed in earlier versions, so keep WPCafe up to date.
Is WPCafe still maintained?
Yes. Its last release was 2 weeks ago. Its authors resolved 1 of the 1 support threads opened in the last two months.
Is WPCafe 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.