LatePoint ≤ 5.7.6: A Two-Word String That Resets Your First Customer's Password (CVE-2026-118066, CVSS 9.1)

Running LatePoint on your site? Check it against CVE-2026-118066 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your LatePoint is in the affected range (≤ 5.7.6), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

LatePoint ≤ 5.7.6: A Two-Word String That Resets Your First Customer's Password (CVE-2026-118066, CVSS 9.1)

The string IS NOT NULL is SQL syntax — part of a query's grammar, never something a visitor should be able to type into a web request and have pasted into a database query verbatim. In LatePoint, the appointment-booking plugin for WordPress (100,000+ active installs), that is exactly what happens in versions up to and including 5.7.6: CVE-2026-118066 turns a public password-change route into an unauthenticated account-takeover route, and the customer it hands over first is the earliest one in your database.

What Happened

CVE-2026-118066 is an unauthenticated authentication bypass vulnerability in the LatePoint plugin for WordPress, disclosed November 7, 2026 (CNA: Wordfence).

This one is version-checkable, and our scanner checks it: the free mini-scan reads the plugin's public readme and flags a stable tag at or below 5.7.6 as a High finding naming CVE-2026-118066. A site on a newer tag earns no claim either way from this check — because the CVE record names no fixed version, a version above the affected range is silence, not a clean bill of health. The check reads the version only; it never calls the AJAX routes, never triggers a password reset, and never exercises the flaw.

Am I Affected?

Check wp-admin → Plugins for LatePoint and its version. At 5.7.6 or below you are in the affected range — and the exposure is your customer list, not just your site: the first account this flaw hands over is your lowest-id customer, which on most booking sites means a real, long-standing customer's bookings, orders, and personal data.

What To Do Now

  1. Update LatePoint to the latest available release today. wordpress.org serves 5.7.8; install the current release and confirm against the vendor changelog. There is no verified "fixed in" version to aim at — latest is the remediation.
  2. Audit customer accounts — especially the earliest-registered ones. This flaw resolves to the lowest-id customer first. Look for password changes you cannot explain, and check the bookings and orders attached to your oldest customer accounts for changes nobody made.
  3. Review linked WordPress accounts. If your site uses the option to treat WordPress users as customers, extend the audit to those accounts — the takeover path reaches them too.
  4. Treat exposed customer data as exposed. If an affected version was live while strangers could reach the booking pages, review what a taken-over customer account could see: names, contact details, booking history. That review is the incident response; the update is only the patch.

The Bigger Lesson

Sentinel strings are not a query-building strategy. The code needed a way to say "this column is not null" inside its own query builder — and implemented it by comparing user-supplied values against SQL keywords and pasting matches into the statement. Every layer that touched the value afterwards (sanitizers, scalar guards) faithfully preserved the attack, because the flaw was never about dirty input; it was about a design that let input become grammar. Values that arrive from a request must only ever be data — bound as parameters, never promoted to syntax, whoever sent them and however clean they look.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the account audit finds a stranger.


Running LatePoint at 5.7.6 or below? Update today, audit your earliest customers, then run the free check at preshipit.com/free-scan — it version-checks this plugin and the rest of your site's announced surface in about a minute.

Check LatePoint on your own site — free.

Our free WordPress Plugin Vulnerability Checker pulls LatePoint's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-118066 included. No scan, no account.

Open the free plugin checker →

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Running LatePoint on your site? Check it against CVE-2026-118066 — free.

The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your LatePoint is in the affected range (≤ 5.7.6), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report