HomeWordPress vulnerabilitiesWPCafe
WPCafe vulnerabilities
WPCafe has 9 known vulnerabilities in this database. The most recent published record is dated 7 Oct 2026.
- Known vulnerabilities
- 9
- Active installs
- 5,000+
- Latest version
- 3.0.21
- Last updated
- 30 Sep 2026
- Most recent
- 7 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Sensitive data exposure CVE-2026-86816 | Medium 5.3 | Before 3.0.21 | Fixed in 3.0.21 | 18 h ago |
| Broken access control CVE-2026-11601 | Medium 5.3 | Up to 3.0.19 | Fixed in a later version (latest 3.0.21) | 4 d ago |
| File inclusion CVE-2026-75028 | High 7.5 | Up to 3.0.18 | Fixed in a later version (latest 3.0.21) | 4 d ago |
| Broken access control CVE-2026-86812 | Medium 6.5 | Before 3.0.18 | Fixed in 3.0.18 | 11 Sep 2026 |
| Broken access control CVE-2026-14550 | Medium 5.3 | Before 3.0.18 | Fixed in 3.0.18 | 26 Aug 2026 |
| Broken access control CVE-2026-11818 | Medium 5.4 | Up to 3.0.14 | Fixed in a later version (latest 3.0.21) | 10 Jul 2026 |
| File inclusion CVE-2024-5431 | High 8.8 | Before 2.2.26 | Fixed in 2.2.26 | 25 Jun 2024 |
| Cross-site scripting (XSS) CVE-2024-5427 | Medium 6.4 | Before 2.2.26 | Fixed in 2.2.26 | 31 May 2024 |
| Server-side request forgery (SSRF) CVE-2024-1855 | Medium 5.3 | Before 2.2.24 | Fixed in 2.2.24 | 23 May 2024 |
Read the published descriptions
- CVE-2026-86816, 7 Oct 2026
- The WPCafe WordPress plugin before 3.0.21 does not restrict access to some of its REST API endpoints, allowing unauthenticated attackers to read WooCommerce product data, including per-product sales counts, exact stock levels, and private product meta, that WooCommerce itself keeps behind authentication. CVE record
- CVE-2026-11601, 3 Oct 2026
- 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. CVE record
- CVE-2026-75028, 3 Oct 2026
- The WPCafe - Restaurant Menu, Online Food Ordering & Table Booking System plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.0.18 via the (template scope) function. This makes it possible for authenticated attackers, with contributor-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. CVE record
- CVE-2026-86812, 11 Sep 2026
- The WPCafe WordPress plugin before 3.0.18 does not correctly restrict access to a set of order-management REST endpoints because their permission callbacks return an incorrect type on failure, allowing unauthenticated users to disclose guest order information and to change the status of, or trash, any order. CVE record
- CVE-2026-14550, 26 Aug 2026
- The WPCafe WordPress plugin before 3.0.18 does not perform an authorization check when creating a reservation through its REST API, verifying only a publicly available nonce, allowing unauthenticated users to submit reservations with an arbitrary approval status and bypass the administrator moderation workflow. CVE record
- CVE-2026-11818, 10 Jul 2026
- 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.14. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to list, create, update, delete, clone, and bulk-delete notification flow workflows that are intended to be managed only by administrators. The only protection on these endpoints is a wp_rest nonce check, which is obtainable by any logged-in user from the frontend page source. CVE record
- CVE-2024-5431, 25 Jun 2024
- The WPCafe - Online Food Ordering, Restaurant Menu, Delivery, and Reservations for WooCommerce plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.2.25 via the reservation_extra_field shortcode parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to include remote files on the server, potentially resulting in code execution CVE record
- CVE-2024-5427, 31 May 2024
- The WPCafe - Online Food Ordering, Restaurant Menu, Delivery, and Reservations for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's Reservation Form shortcode in all versions up to, and including, 2.2.24 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2024-1855, 23 May 2024
- The WPCafe - Restaurant Menu, Online Ordering for WooCommerce, Pickup / Delivery and Table Reservation plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.2.23 via the wpc_check_for_submission function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application. CVE record
What to do if you run WPCafe
If you run WPCafe, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WPCafe vulnerabilities
Free. We email you when a new vulnerability is published for WPCafe, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.