WP Time Slots Booking Form
wp-time-slots-booking-form · plugin
Known security vulnerabilities for WP Time Slots Booking Form. Find out in seconds which version runs on your site with WP Lens.
11 known vulnerabilities
1 critical · 6 exploitable without logging in · 1 with public exploit code · latest Jun 15, 2026
Listed on wordpress.org · latest 1.2.54 · last updated Aug 17, 2026 · 1K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Critical 9.8
CVE-2024-35735unauthenticated≤ 1.2.11
WordPress WP Time Slots Booking Form plugin <= 1.2.11 - Broken Access Control vulnerability
- High 8.8
CVE-2022-41790login required≤ 1.1.76
WordPress WP Time Slots Booking Form Plugin <= 1.1.76 is vulnerable to Broken Access Control
- High 8.5
CVE-2026-48882subscriber+≤ 1.2.50
WordPress WP Time Slots Booking Form plugin <= 1.2.50 - SQL Injection vulnerability
- High 7.5
CVE-2024-33543unauthenticated≤ 1.2.06
WordPress WP Time Slots Booking Form plugin <= 1.2.06 - Broken Access Control vulnerability
- High 7.2
CVE-2023-23895high privilege≤ 1.1.82
WordPress WP Time Slots Booking Form plugin <= 1.1.82 - Broken Access Control vulnerability
- High 7.1
CVE-2026-40791unauthenticated · needs a click≤ 1.2.46
WordPress WP Time Slots Booking Form plugin <= 1.2.46 - Cross Site Scripting (XSS) vulnerability
- Medium 6.5
CVE-2025-68569login required≤ 1.2.39
WordPress WP Time Slots Booking Form plugin <= 1.2.39 - Broken Access Control vulnerability
- Medium 6.1
CVE-2024-35734unauthenticated · needs a click≤ 1.2.10
WordPress WP Time Slots Booking Form plugin <= 1.2.10 - Cross Site Scripting (XSS) vulnerability
- Medium 5.3
CVE-2026-32432unauthenticated≤ 1.2.42
WordPress WP Time Slots Booking Form plugin <= 1.2.42 - Broken Access Control vulnerability
- Medium 4.8
CVE-2023-23971admin≤ 1.1.81
WordPress WP Time Slots Booking Form Plugin <= 1.1.81 is vulnerable to Cross Site Scripting (XSS)
- Medium 4.3
CVE-2025-49332unauthenticated · needs a click≤ 1.2.30
WordPress WP Time Slots Booking Form plugin <= 1.2.30 - 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).