CyberRota Analysis
AI-GeneratedThe Bookly plugin for WordPress is vulnerable to Insecure Direct Object Reference, allowing unauthenticated attackers to exploit AJAX actions to access and manipulate sensitive data. This vulnerability enables attackers to enumerate order IDs, disclose other customers' order tokens, retrieve appointment information, and delete bookings, posing a significant risk to user privacy and data integrity. WordPress site administrators using the affected versions of the Bookly plugin should prioritize applying the necessary patches to mitigate these critical risks.
Original NVD Description
The Bookly plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 28.2 via the 'bookly_get_form_id', 'bookly_render_complete', 'bookly_add_to_calendar' and 'bookly_rollback_order' AJAX actions. This is due to the 'bookly_get_form_id' handler blindly storing the attacker-controlled 'order_id' from the submitted form_data into a new booking session, which the 'bookly_render_complete' handler then trusts to look up and return the corresponding Order's secret token without verifying that the current session created that order. This makes it possible for unauthenticated attackers to enumerate sequential order IDs, disclose other customers' order tokens, retrieve calendar/appointment information via 'bookly_add_to_calendar' and permanently delete arbitrary non-completed bookings via 'bookly_rollback_order', which cascade-deletes the customer_appointment and (when no other customers are attached) the underlying appointment.