ReDi Restaurant Reservation – Instant Restaurant Booking & Table Reservation System
redi-restaurant-reservation · plugin
Known security vulnerabilities for ReDi Restaurant Reservation – Instant Restaurant Booking & Table Reservation System. Find out in seconds which version runs on your site with WP Lens.
7 known vulnerabilities
6 exploitable without logging in · latest May 23, 2025
Listed on wordpress.org · latest 26.4.0 · last updated Oct 2, 2026 · 700+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 7.3
CVE-2023-36510unauthenticated≤ 23.0211
WordPress ReDi Restaurant Reservation plugin <= 23.0211 - Broken Access Control vulnerability
- High 7.1
CVE-2025-48286unauthenticated · needs a click≤ 24.1209
WordPress ReDi Restaurant Reservation plugin <= 24.1209 - Reflected Cross Site Scripting (XSS) vulnerability
- High 7.1
CVE-2024-31299unauthenticated · needs a click≤ 24.0128
WordPress ReDi Restaurant Reservation plugin <= 24.0128 - Cross Site Request Forgery (CSRF) to XSS vulnerability
- Medium 6.1
CVE-2024-9240unauthenticated · needs a click≤ 24.0902
ReDi Restaurant Reservation <= 24.0902 - Reflected Cross-Site Scripting
- Medium 6.1
CVE-2024-29806unauthenticated · needs a click≤ 24.0128
WordPress ReDi Restaurant Reservation plugin <= 24.0128 - Reflected Cross Site Scripting (XSS) vulnerability
- Medium 5.4
CVE-2024-38737login required≤ 24.0422
WordPress ReDi Restaurant Reservation plugin <= 24.0422 - Broken Access Control vulnerability
- Medium 4.3
CVE-2024-31385unauthenticated · needs a click≤ 24.0128
WordPress ReDi Restaurant Reservation plugin <= 24.0128 - Cross Site Request Forgery (CSRF) 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).