Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress
bookingpress-appointment-booking · plugin
Known security vulnerabilities for Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress. Find out in seconds which version runs on your site with WP Lens.
19 known vulnerabilities
3 critical · 9 exploitable without logging in · 1 with public exploit code · latest Aug 29, 2026
Before you install
Do not install
- Closed on wordpress.org on Feb 1, 2025; no updates will come.
- 3 records needing no login published in the last two years.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Closed on wordpress.org
Removed from the directory on Feb 1, 2025 · reason: guideline violation. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Nov 15, 2026
Vulnerabilities
- Critical 9.8
CVE-2024-7350unauthenticated≤ 1.1.7
Appointment Booking Calendar Plugin and Online Scheduling Plugin – BookingPress 1.1.6 - 1.1.7 - Authentication Bypass to Account Takeover
- Critical 9.8
CVE-2023-51405unauthenticated≤ 1.0.74
WordPress BookingPress plugin <= 1.0.74 - Booking Price Manipulation vulnerability
- Critical 9.8
CVE-2022-0739unauthenticated→ 1.0.11
BookingPress < 1.0.11 - Unauthenticated SQL Injection
- High 8.8
CVE-2024-6660subscriber+≤ 1.1.5
BookingPress – Appointment Booking Calendar Plugin and Online Scheduling Plugin <= 1.1.5 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Option
- High 8.8
CVE-2024-6467subscriber+≤ 1.1.5
BookingPress Appointment Booking <= 1.1.5 - Authenticated (Subscriber+) Arbitrary File Read to Arbitrary File Creation
- High 8.8
CVE-2023-50841login required≤ 1.0.72
WordPress BookingPress Plugin <= 1.0.72 is vulnerable to SQL Injection
- High 8.1
CVE-2026-12378unauthenticated≤ 1.1.28
BookingPress <= 1.1.28 - Unauthenticated PHP Object Injection
- High 7.6
CVE-2025-31910high privilege≤ 1.1.28
WordPress BookingPress plugin <= 1.1.28 - SQL Injection vulnerability
- High 7.5
CVE-2026-76586unauthenticated→ 1.6.3
BookingPress 1.5.6 - 1.6.2 - Unauthenticated Booking Price Manipulation via PayPal Payment Confirmation
- High 7.5
CVE-2024-12274unauthenticated→ 1.1.23
BookingPress < 1.1.23 - Unauthenticated Export File Download
- High 7.2
CVE-2024-3022admin≤ 1.0.87
BookingPress – Appointment Booking Calendar Plugin and Online Scheduling Plugin <= 1.0.87 - Authenticated (Admin+) Arbitrary File Upload
- High 7.2
CVE-2023-6219admin≤ 1.0.76
BookingPress <= 1.0.76 - Authenticated (Administrator+) Arbitrary File Upload
- Medium 6.5
CVE-2024-10540subscriber+≤ 1.1.16
Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress <= 1.1.16 - Authenticated (Subscriber+) SQL Injection
- Medium 6.5
CVE-2024-11726contributor+≤ 1.1.21
Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress <= 1.1.21 - Authenticated (Contributor+) SQL Injection
- Medium 5.4
CVE-2025-24732login required≤ 1.1.25
WordPress BookingPress Plugin <= 1.1.25 - Cross Site Scripting (XSS) vulnerability
- Medium 5.4
CVE-2024-31296login required≤ 1.0.81
WordPress BookingPress plugin <= 1.0.81 - Insecure Direct Object References (IDOR) vulnerability
- Medium 5.3
CVE-2024-34799unauthenticated≤ 1.0.82
WordPress BookingPress plugin <= 1.0.82 - Appointment Duration Manipulation vulnerability
- Medium 5.3
CVE-2023-36507unauthenticated≤ 1.0.64
WordPress BookingPress Plugin <= 1.0.64 is vulnerable to Sensitive Data Exposure
- Medium 5.3
CVE-2022-4340unauthenticated→ 1.0.31
BookingPress < 1.0.31 - Unauthenticated IDOR in appointment_id
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).
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.