On this page (7 sections)
A critical vulnerability, CVE-2026-118066, affects the LatePoint appointment booking and scheduling plugin for WordPress. According to the GitHub Advisory Database entry, an unauthenticated attacker can overwrite a customer's password through a public AJAX route and then log in as that customer. All versions up to and including 5.7.6 are described as vulnerable.
If your site takes bookings through LatePoint, especially with customer accounts enabled, you should check your installed version today and plan mitigation. At the time of writing, the advisory does not name a fixed version.
What happened
The vulnerability was published on November 7, 2026 via the National Vulnerability Database and the GitHub Advisory Database. The description attributes it to the plugin's data-model code: a helper that builds database query conditions treats the literal text values IS NULL and IS NOT NULL specially and inserts them straight into the SQL statement instead of passing them as bound parameters.
Because the attacker controls those values through request parameters, they can make a password-reset lookup match customer records rather than the one tied to a genuine reset token. The advisory states that this requires no login, no privileges and no user interaction, which is why the score is so high.
Only one independent publisher covers this so far. The NVD entry repeats the same text as the GitHub advisory, so treat it as one source, not two confirmations. The GitHub advisory also shows as unreviewed.
How the weakness works
This is an authentication bypass caused by unsafe query construction. Normally a password reset flow says: find the customer whose secret reset token equals the value in the request. Here, the code compares the supplied value to two special strings before building the query. If it matches one of them, the string is concatenated into the SQL as a keyword. The query then effectively asks for any customer who has a non-empty token, instead of the one with a specific token.
The advisory says this slips past two existing protections: the standard WordPress text sanitizer and a scalar-type check added in version 5.7.5, because both let a plain string pass unchanged. The advisory therefore lists the affected range as running through 5.7.6, so the 5.7.5 hardening should not be treated as a fix.
What an attacker could gain
- Per the advisory, the password of the lowest-id customer is overwritten with a value the attacker chooses, giving access to that customer's bookings, orders and personal information.
- The attacker can first learn the target's name and email through a second public route that returns details from the first matching order intent.
- The advisory says the attacker can also trigger a reset themselves to satisfy the required 15-minute freshness window.
- If the wp_users_as_customers option is enabled, the takeover extends to the linked WordPress subscriber or customer-role account.
The advisory describes impact on confidentiality and integrity, not availability. It does not describe a path to administrator access. A takeover of a linked account is still serious on sites where customer-role accounts can see more than bookings, such as shops.
Who is affected
Any WordPress site with the LatePoint plugin active at version 5.7.6 or lower is in scope. The vulnerable routes are described as public, so exposure does not depend on having logged-in users. Sites that use the customer cabinet (the customer login and password reset area) and those that link customers to WordPress users face the most direct risk. Sites that hold personal data in bookings, such as clinics, salons, consultants and service businesses, should treat a takeover as a potential personal data incident.
How to check your exposure
First confirm whether LatePoint is installed and which version it runs. The WP-CLI command below is read-only: run it from your WordPress root and look at the version column for the latepoint row. Anything at 5.7.6 or lower is affected.
wp plugin list --name=latepoint --fields=name,status,versionIf you do not have shell access, open Plugins in the WordPress dashboard and read the version under LatePoint. You can also compare against the known vulnerabilities per plugin list and read our guide on whether your WordPress plugin is vulnerable.
Then look for signs of misuse in your web server access logs. The search below is read-only: it lists requests that mention the two routes named in the advisory. Adjust the log path for your server. A burst of requests from one address, or requests to the password change route you cannot explain, deserve a closer look.
grep -E 'customer_cabinet__change_password|steps__start_from_order_intent' /var/log/nginx/access.logWhat to do now
No fixed version is named in the advisory, so check the plugin's official listing and the vendor's channels for a release newer than 5.7.6 before deciding between updating and temporary mitigation.
- Identify every site you manage that runs LatePoint and record the installed version.
- Check the WordPress plugin directory and the vendor's changelog for a release newer than 5.7.6, and update as soon as one is confirmed to address CVE-2026-118066. Back up the site first.
- If no fixed release exists, consider deactivating the plugin or taking the booking pages offline until one is available, weighing the business impact.
- Review recent customer password changes and reset emails. Force password resets for customer accounts if you see unexplained activity, and tell affected customers if personal data may have been exposed.
- If wp_users_as_customers is enabled, review subscriber and customer-role accounts for unexpected logins or changes.
- Review access logs for the two routes named above and for unusual spikes in requests to admin-ajax.php.
- Tell customers who reuse passwords to change them elsewhere if you confirm a compromise.
Detection and monitoring afterwards
Account takeover leaves traces in user behavior rather than in files, so monitor the application. Watch for password-change emails customers did not request, logins from new locations, and changes to customer email addresses. Keep plugins on a regular update schedule and remove any you no longer use. Our WordPress security checklist covers the baseline.
Webforta also offers read-only security scans for sites you verify, which can help you keep track of exposed components, though no outside tool can see inside your database or confirm that a given account was not taken over. If you suspect compromise, follow Website hacked: what to do.
Timeline
| Date | Event |
|---|---|
| Nov 7, 2026 | CVE-2026-118066 published by NVD and added to the GitHub Advisory Database |
| Nov 7, 2026 | GitHub advisory last updated; patched versions listed as unknown |
The advisory references a Wordfence vulnerability entry and the plugin's public code repository for version 5.7.5. We will not describe exploit details beyond what the advisory says, and details may change as the vendor responds.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
