WPCafe <= 3.0.19 - Missing Authorization to Unauthenticated Arbitrary Email Notification Flow Read/Create/Update/Delete
Strategic Overview
- Status
- Patched in 3.0.20
- Affected Version
<= 3.0.19- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-11601
At a glance
CVE-2026-11601 is a medium-severity Missing Authorization vulnerability in the WPCafe WordPress plugin, affecting versions <= 3.0.19. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.0.20; sites on affected versions should update now. Disclosed October 2026, reported by Niv Kochan.
Vulnerability Overview
The WPCafe – Restaurant Menu, Online Food Ordering & Table Booking System plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.0.19. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to read, create, update, clone, and delete email notification flows, including overwriting the default reservation confirmation, cancellation, and admin alert emails with attacker-controlled content sent from the site's legitimate address, or destroying reservation notification flows entirely. The vulnerable endpoints are active by default on every WPCafe installation without any configuration requirement, as the Email_Automation_Service_Provider::is_enable() method unconditionally returns true and the plugin ships with five pre-configured default email flows upon activation.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
WPCafe <= 3.0.19 carries this weakness at is_enable(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WPCafe the fix is 3.0.20: builds <= 3.0.19 are affected, anything from 3.0.20 onward is not.
Remediation
Update to version 3.0.20, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WPCafe 3.0.20 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WPCafe – Restaurant Menu, Online Food Ordering & Table Booking System
- 8.8CVE-2025-39452: WPCafe <= 2.2.32 Local File Inclusion
CVE-2025-39452 - 8.8CVE-2025-30829: WPCafe <= 2.2.31 Local File Inclusion
CVE-2025-30829 - 8.8CVE-2024-43135: WPCafe <= 2.2.28 Local File Inclusion
CVE-2024-43135 - 8.8CVE-2024-37513: WPCafe <= 2.2.27 Local File Inclusion
CVE-2024-37513 - 8.8CVE-2024-5431: WPCafe File inclusion
CVE-2024-5431 - 7.5CVE-2026-75028: WPCafe <= 3.0.18 Local File Inclusion
CVE-2026-75028 - 7.2WPCafe XSS
- 6.4CVE-2024-5427: WPCafe Stored XSS
CVE-2024-5427
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C