WPPizza – A Restaurant Plugin
wppizza · plugin
Known security vulnerabilities for WPPizza – A Restaurant Plugin. Find out in seconds which version runs on your site with WP Lens.
7 known vulnerabilities
4 exploitable without logging in · latest Jun 15, 2026
Listed on wordpress.org · latest 3.20.1 · last updated Jun 9, 2026 · 1K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 7.1
CVE-2025-26991unauthenticated · needs a click≤ 3.19.4
WordPress WPPizza plugin <= 3.19.4 - Reflected Cross Site Scripting (XSS) vulnerability
- Medium 6.5
CVE-2026-40796subscriber+≤ 3.19.9
WordPress WPPizza plugin <= 3.19.9 - Sensitive Data Exposure vulnerability
- Medium 6.5
CVE-2024-33576login required≤ 3.18.10
WordPress WPPizza plugin <= 3.18.10 - Broken Access Control vulnerability
- Medium 6.1
CVE-2024-35766unauthenticated · needs a click≤ 3.18.13
WordPress WPPizza – A Restaurant Plugin plugin <= 3.18.13 - Reflected Cross Site Scripting (XSS) vulnerability
- Medium 6.1
CVE-2023-46622unauthenticated · needs a click≤ 3.18.2
WordPress WPPizza Plugin <= 3.18.2 is vulnerable to Cross Site Scripting (XSS)
- Medium 6.1
CVE-2023-32105unauthenticated · needs a click≤ 3.17.1
WordPress WPPizza Plugin <= 3.17.1 is vulnerable to Cross Site Scripting (XSS)
- Medium 4.3
CVE-2025-57894login required≤ 3.19.8
WordPress WPPizza Plugin <= 3.19.8 - Broken Access Control Vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).