Summary
This advisory addresses CVE-2026-118066, an Authentication Bypass via Account Takeover vulnerability. It affects the Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress. A security fix is available in version 5.7.7. There is no evidence of active exploitation at this time.
Affected and patched versions
Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress (plugin latepoint): affected 5.7.6 and earlier; fixed in 5.7.7
Is my site vulnerable?
To determine if your WordPress site is vulnerable, check the version of the Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress installed.
Log in to your WordPress administrator dashboard.
Navigate to the "Plugins" section and select "Installed Plugins".
Locate "Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress" in the list.
Examine the version number displayed next to the plugin name.
Your site is vulnerable if the installed version is 5.7.6 or any earlier release. Sites running version 5.7.7 or newer are not affected by this specific vulnerability.
What an attacker actually does
The core vulnerability lies within the OsModel::build_conditions_query() function, located in the lib/models/model.php file of the LatePoint plugin. This function is responsible for constructing database WHERE-clauses. A flaw exists in how it handles certain input values: it directly compares incoming WHERE-clause values against the literal strings 'IS NULL' and 'IS NOT NULL'. If a match occurs, the function concatenates this string directly into the SQL query without proper parameter binding. This bypasses standard security measures, including sanitize_text_field() and the is_scalar() hardening guard introduced in version 5.7.5, as these functions pass the scalar sentinel through unchanged.
This specific vulnerability allows an unauthenticated attacker to perform an authentication bypass leading to account takeover. The attacker initiates this process by sending a specially crafted request to a public AJAX route, customer_cabinet__change_password. Within this request, the attacker includes params[password_reset_token]=IS NOT NULL. Due to the flawed build_conditions_query() function, this IS NOT NULL value is interpreted directly by the database. It causes the query to match every customer record where the account_nonse value is not null. The system then resolves this broad match to the customer with the lowest ID.
Once the lowest-ID customer is identified, the attacker can overwrite that customer's password with a value of their choosing. This grants the attacker full access to the compromised customer's account. This access includes all associated bookings, orders, and personally identifiable information (PII) stored within the LatePoint plugin. When the WordPress installation has the wp_users_as_customers option enabled, the attacker gains control over the linked WordPress subscriber or customer-role account, expanding the scope of the compromise beyond the plugin's data.
Before executing the password reset, an attacker can identify a target customer's email address. This is achieved by sending params[order_intent_key]=IS NOT NULL to another public route, steps__start_from_order_intent. This action returns the name and email address from the first matching order intent found in the system. With the target customer's email, the attacker can then trigger a legitimate password reset for that customer. This step is crucial because it arms the required 15-minute password-reset freshness window, making the subsequent account takeover attempt via the IS NOT NULL sentinel viable within the system's expected reset timeframe.
How to detect a compromise
Detecting a compromise related to CVE-2026-118066 involves reviewing specific activities and data points within your WordPress installation and LatePoint plugin. Since this vulnerability facilitates account takeover, indicators of compromise will primarily revolve around unauthorized access and modifications to customer accounts.
Administrators should review customer accounts for any unexpected password resets. This includes checking if customers report being locked out of their accounts or receiving password reset emails they did not request. Similarly, look for unfamiliar logins to customer accounts, especially those associated with the lowest customer IDs, as these are the primary targets of this attack.
Examine the LatePoint plugin's internal logs or any available WordPress audit logs for unusual activity on the customer_cabinet__change_password and steps__start_from_order_intent AJAX routes. While specific log locations may vary, look for multiple or repeated requests to these endpoints from unfamiliar IP addresses, particularly those containing IS NOT NULL in their parameters.
Review customer data for unauthorized changes to bookings, appointments, or personal information. Any discrepancies in customer profiles, such as altered contact details or booking cancellations or creations not initiated by the legitimate customer, could indicate a compromise. If the wp_users_as_customers option is enabled, also check the WordPress user list for any unauthorized password changes or suspicious activity on subscriber or customer-role accounts. Direct database inspection can also reveal signs of compromise. Examine the account_nonse values and password hashes in the LatePoint customer tables for recent, unexplained modifications.
How to fix
To prevent further exploitation and address this vulnerability, follow these steps:
Immediately update LatePoint to the latest available release, version 5.7.7 or higher.
Review customer accounts for unexpected password resets or unfamiliar logins. If any are found, reset the affected customer's password and advise them to use a strong, unique password.
If an update is not promptly possible, consider restricting or filtering access to the plugin's public AJAX endpoints, specifically
customer_cabinet__change_passwordandsteps__start_from_order_intent, through a web application firewall (WAF) or server-level rules. This is a temporary mitigation and should be replaced with an update as soon as possible.
Timeline
Date | Event |
|---|---|
2026-10-26 | Version release |
2026-11-02 | Security fix release |
2026-11-07 | NVD record published |