10267 matches found
CVE-2026-105195 Booking Calendar 10.15 - 11.8.2 - Editor+ Arbitrary Option Disclosure
The Booking Calendar WordPress plugin before 11.8.3 does not adequately restrict which options a lower-privileged user can load through one of its settings handlers, allowing users with the Editor role and above to disclose the values of arbitrary WordPress options, including core site...
CVE-2026-105193
The Booking Calendar WordPress plugin, in versions before 11.8 , is vulnerable to unauthenticated booking information disclosure and modification. The root cause is the use of insufficient entropy when generating per-booking access hashes, as they are derived from a low-entropy time-seeded value ...
EUVD-2026-94767
The Booking Calendar WordPress plugin before 11.8.3 does not adequately restrict which options a lower-privileged user can load through one of its settings handlers, allowing users with the Editor role and above to disclose the values of arbitrary WordPress options, including core site...
CVE-2026-105195
The Booking Calendar WordPress plugin (versions 10.15 - 11.8.2 ) contains a vulnerability where it fails to adequately restrict which options a lower-privileged user can load through one of its settings handlers . This flaw allows users with the Editor role and above to disclose the values of arb...
EUVD-2026-94765
The Booking Calendar WordPress plugin before 11.8 does not generate its per-booking access hashes with sufficient entropy, deriving each from a low-entropy time-seeded value, which can allow unauthenticated attackers who are able to determine a booking's creation time to predict the hash and then...
WordPress Booking Calendar plugin 10.15-11.8.2 - Editor+ Arbitrary Option Disclosure vulnerability
Editor+ Arbitrary Option Disclosure vulnerability discovered by vuxvinh in WordPress Plugin Booking Calendar versions 10.15-11.8.2...
WordPress Booking Calendar plugin < 11.8 - Unauthenticated Booking Information Disclosure and Modification vulnerability
Unauthenticated Booking Information Disclosure and Modification vulnerability discovered by Olaf Schigt in WordPress Plugin Booking Calendar versions 11.8...
CVE-2026-105193: Inadequate Encryption Strength
The Booking Calendar WordPress plugin before 11.8 does not generate its per-booking access hashes with sufficient entropy, deriving each from a low-entropy time-seeded value, which can allow unauthenticated attackers who are able to determine a booking's creation time to predict the hash and then...
CVE-2026-105195: Exposure of Sensitive Information to an Unauthorized Actor
The Booking Calendar WordPress plugin before 11.8.3 does not adequately restrict which options a lower-privileged user can load through one of its settings handlers, allowing users with the Editor role and above to disclose the values of arbitrary WordPress options, including core site...
CVE-2026-105198: Authorization Bypass Through User-Controlled Key
The Appointment Booking Plugin WordPress plugin before 5.7.3 does not verify that the caller owns the order referenced by an order-item identifier before rendering that order's confirmation summary, letting an unauthenticated visitor retrieve any customer's name, contact details and order...
CVE-2026-17538: Authorization Bypass Through User-Controlled Key
The LatePoint - Appointment Booking & Reservation plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 5.6.9. This is due to the processstepcustomer function using isuserloggedin as the sole gate before merging POSTed customer data into an...
CVE-2026-105196: Authorization Bypass Through User-Controlled Key
The Appointment Booking Plugin WordPress plugin before 5.6.9 does not enforce per-record authorization on several of its AI Abilities API actions, allowing an authenticated user holding the LatePoint Agent role, normally restricted to their own records, to read and modify other agents' profile da...
CVE-2026-105197: Authorization Bypass Through User-Controlled Key
The Appointment Booking Plugin WordPress plugin before 5.6.5 does not verify that a backend staff user is authorized to act on the specific record targeted for deletion, allowing an authenticated user with a record-scoped staff role to irreversibly delete any order, customer, or transaction on th...
PT-2026-107837
The Appointment Booking Plugin WordPress plugin before 5.7.3 does not verify that the caller owns the order referenced by an order-item identifier before rendering that order's confirmation summary, letting an unauthenticated visitor retrieve any customer's name, contact details and order...
PT-2026-107835
The Appointment Booking Plugin WordPress plugin before 5.6.9 does not enforce per-record authorization on several of its AI Abilities API actions, allowing an authenticated user holding the LatePoint Agent role, normally restricted to their own records, to read and modify other agents' profile da...
PT-2026-107834
The Booking Calendar WordPress plugin before 11.8.3 does not adequately restrict which options a lower-privileged user can load through one of its settings handlers, allowing users with the Editor role and above to disclose the values of arbitrary WordPress options, including core site...
PT-2026-107836
The Appointment Booking Plugin WordPress plugin before 5.6.5 does not verify that a backend staff user is authorized to act on the specific record targeted for deletion, allowing an authenticated user with a record-scoped staff role to irreversibly delete any order, customer, or transaction on th...
PT-2026-107832
The Booking Calendar WordPress plugin before 11.8 does not generate its per-booking access hashes with sufficient entropy, deriving each from a low-entropy time-seeded value, which can allow unauthenticated attackers who are able to determine a booking's creation time to predict the hash and then...
CVE-2026-17538
The LatePoint - Appointment Booking & Reservation plugin for WordPress (versions
PT-2026-107719
Name of the Vulnerable Software and Affected Versions LatePoint - Appointment Booking & Reservation plugin for WordPress versions prior to 5.7.0 Description An Insecure Direct Object Reference exists because the process step customer function relies solely on is user logged in to validate request...