CVE-2026-119152

The LatePoint plugin for WordPress up to version 5.4.0 has an improper input validation vulnerability in the Stripe Connect payment processor. This allows unauthenticated attackers to pay arbitrary amounts by supplying a previously successful PaymentIntent token.

The LatePoint plugin for WordPress is vulnerable to authentication bypass via account takeover in versions up to and including 5.7.6. OsModel::build_conditions_query() compares WHERE-clause values against literal strings 'IS NULL' and 'IS NOT NULL' and concatenates a match directly into SQL without binding, allowing unauthenticated attackers to send params[password_reset_token]=IS NOT NULL to the public customer_cabinet__change_password AJAX route and overwrite the lowest-id customer's password.

The LatePoint plugin for WordPress in versions up to and including 5.7.4 is vulnerable to Authentication Bypass via Race Condition in the verifyOTP function. The OTP attempts counter is updated non-atomically without a WHERE attempts < 10 guard and without a row lock, creating a TOCTOU window that lets concurrent requests bypass the 10-attempt lockout.

The LatePoint plugin for WordPress contains a Blind SQL Injection vulnerability due to improper neutralization of special elements in SQL commands. This issue affects versions up to and including 5.6.3.

The Appointment Booking Plugin – LatePoint 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 public `steps__reload_booking_form_summary_panel` and `steps__start` routes. The lack of ownership checks allows unauthenticated attackers to enumerate booking and cart identifiers and read other customers' appointment details and pending checkout contents directly from JSON responses.

The Appointment Booking Plugin – LatePoint for WordPress is vulnerable to Authentication Bypass in versions up to and including 5.7.2 via the OsCustomerHelper::create_wp_user_for_customer() helper reached from the public process_step_customer() booking step. When the 'Use WordPress users as customers' option is enabled, the helper matches a WordPress user by user_login equal to the victim's email even if their user_email differs, and links that user's ID into the victim's LatePoint customer row. This allows authenticated attackers with Subscriber-level access to take over another customer's LatePoint account.

The LatePoint plugin for WordPress up to version 5.7.3 is vulnerable to privilege escalation. The lack of an allowlist for setting names/values and missing role validation for the 'default_wp_role_for_customer' setting allows authenticated attackers with 'settings__edit' capability (e.g., agents) to overwrite the default WordPress role to 'administrator', causing new customer accounts to be created with full admin privileges.

The LatePoint plugin for WordPress up to version 5.6.9 is vulnerable to Insecure Direct Object Reference. The process_step_customer() function uses only is_user_logged_in() as a gate before merging POSTed customer data into an existing LatePoint customer, without ownership checks. This allows authenticated attackers with Subscriber-level access or above to modify personal information of arbitrary LatePoint customers, and when contact_merge is 'phone', overwrite the victim's email and take over the account via password reset.

The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to and including 5.6.3 via the LatePointAbilityDeleteBooking::execute due to missing validation on a user controlled key. Attackers with LatePoint Agent-level access or above can read bookings and customer PII (full name, email, phone, and notes) assigned to other agents, and delete arbitrary bookings. This vulnerability is only exploitable when an administrator has enabled the Abilities API toggles.

The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to and including 5.6.9 via the set_customer_object due to missing validation on a user controlled key. This allows unauthenticated attackers to enumerate arbitrary customer records and disclose personally identifiable information - including first name, last name, email address, and phone number - by iterating the customer[id] parameter. This issue is exploitable only when the site is configured with customer authentication disabled (guest checkout enabled).