Unknown Booking For Appointments And Events Calendar vulnerabilities
9 vulnerabilities
Known vulnerabilities in Unknown Booking For Appointments And Events Calendar, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2026-77689unknownbooking for appointments and events calendar+1
EPSS score0.30%
The Booking for Appointments and Events Calendar WordPress plugin before 9.8.1 does not verify that a payment was actually taken before recording a booking as paid, trusting the payment gateway named in a public, unauthenticated booking request even when the site has never configured that gateway. This lets an unauthenticated attacker obtain confirmed, fully paid appointments and events without any payment being collected.CVE-2026-77704unknownbooking for appointments and events calendar+1EPSS score0.28%
The Booking for Appointments and Events Calendar WordPress plugin before 2.4.9 does not check that a user holds the required capability before letting them change an appointment's status, allowing customers to set arbitrary statuses on appointments they are booked on, including approving their own bookings that were left awaiting approval and overwriting another customer's booking status on a shared appointment.CVE-2026-77705unknownbooking for appointments and events calendar+1EPSS score0.46%
The Booking for Appointments and Events Calendar WordPress plugin before 2.4.10 does not verify that the user editing a customer or employee record is entitled to modify the WordPress account linked to it, allowing users holding Amelia's customer or employee management permissions to set the password and email address of other users' WordPress accounts and take them over.CVE-2026-14214unknownbooking for appointments and events calendar+1EPSS score0.28%
The Booking for Appointments and Events Calendar WordPress plugin before 2.4.4 does not restrict which fields can be written through its customer import, allowing a user with the Amelia Manager role to modify arbitrary columns of any stored user record by supplying them in the import request.CVE-2026-14215unknownbooking for appointments and events calendar+1EPSS score0.30%
The Booking for Appointments and Events Calendar WordPress plugin before 2.4.9 does not require authentication or a valid request token before running the post-booking action chain, allowing an unauthenticated user to trigger booking notifications and integration callbacks for a booking by enumerating its identifier.CVE-2026-14212unknownbooking for appointments and events calendar+1EPSS score0.20%
The Booking for Appointments and Events Calendar WordPress plugin before 9.8 does not verify that an authenticated employee (provider) owns the provider account being updated, allowing any employee with an Employee Panel login to overwrite another employee's cabinet password and take over their account.CVE-2026-14211unknownbooking for appointments and events calendar+1EPSS score0.26%
The Booking for Appointments and Events Calendar WordPress plugin before 9.7 does not verify that an authenticated employee (provider) is related to the customer whose record is being accessed, allowing any employee with an Employee Panel login to read and modify the stored personal data of any customer by enumerating sequential identifiers.CVE-2026-14216unknownbooking for appointments and events calendar+1EPSS score0.30%
The Booking for Appointments and Events Calendar WordPress plugin before 2.4.7 does not require authentication before processing its pending notification queue, allowing an unauthenticated user to force the dispatch of queued notifications and integration callbacks.CVE-2026-14213unknownbooking for appointments and events calendar+1EPSS score0.26%
The Booking for Appointments and Events Calendar WordPress plugin before 2.4.6 does not verify that an authenticated employee (provider) is assigned to the appointment being accessed, allowing any employee to read any appointment by its identifier and disclose the booked customer's personal data.