The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.7.3 via the 'params[customer][firstname]' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract privileged booking data including the administrator-only adminnotes field, assigned agent internal contact details, transaction tokens, and payment request URLs delivered via rendered notification emails. A LatePoint customer can exploit this by storing a template placeholder such as {{customeradminnotes}} in their own firstname field via the customercabinetupdate route, then triggering the password-reset email flow to receive the expanded value in the resulting notification.

The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 5.7.3 via the booking[id] and cart[id] parameters on the stepsreloadbookingformsummarypanel and stepsstart public routes (reachable through wpajaxnoprivlatepointroutecall). This is due to OsStepsHelper::setrequiredobjects() feeding raw request parameters into setbookingobject() and setcartobject(), which call OsModel::setdata() and load an arbitrary booking or cart row by primary key with no ownership check — the ownership guard the vendor added for the earlier disclosure lives only inside OsStepsHelper::loadstep() and does not cover the sibling routes or cart[id] at all. This makes it possible for unauthenticated attackers to enumerate sequential booking / cart identifiers and read other customers' appointment details (service name, agent, date/time, duration, price breakdown, status) and other shoppers' pending checkout contents directly from the JSON responses.