← All security briefings

Attention

LatePoint booking plugin: customer account takeover via password reset (CVE-2026-118066)

Identifiers: CVE-2026-118066

Published
Last substantive change
Last verified

Last verified: . Attention items are due for re-verification within 72 hours.

Summary

Wordfence published CVE-2026-118066 on 6 November 2026 for the LatePoint WordPress plugin, slug latepoint, versions 5.7.6 and earlier. The fix is 5.7.7, dated 2 November in the vendor changelog as security hardening credited to Wordfence. The current release 5.7.8, dated 3 November, contains further security changes; the vendor does not say they address this CVE. The vendor fix dates precede the 6 November advisory. The flaw is in how the public customer password reset handles its reset token.

Classification reason: Checked as of 17 November 2026. Advisory published 6 November; patched releases 5.7.7 and 5.7.8 are available, so update now and review accounts for prior misuse. Wordfence telemetry observed on 17 November reports attack attempts blocked in the preceding 24 hours, so sites on 5.7.6 or earlier should not delay the update.

Impact

An unauthenticated attacker can take over a matching customer account, gaining access to bookings, orders and personal data. If the wp_users_as_customers option is enabled, the linked WordPress subscriber or customer account can also be taken over. This is not a universal WordPress administrator takeover.

Who is affected

Sites running the latepoint plugin at 5.7.6 or earlier with the public customer password reset reachable. The attack needs a matching customer record whose stored reset token is non-NULL within a valid 15-minute reset window. An attacker can initiate that window, so no prior reset request by the victim is required.

Products and versions

Products and versionsAffectedFixed
LatePoint appointment booking plugin for WordPress <= 5.7.6 5.7.7 or a newer patched release; vendor current release 5.7.8 adds further security changes.

Exploitation evidence

Exploitation reported. Wordfence reports blocking 1,635 attack attempts targeting this vulnerability in the 24 hours preceding its report, as observed on 17 November 2026. These are aggregate firewall-blocked attempts only. The reviewed sources report no successful compromise, no count of affected sites, and no independent confirmation.

Sources: Wordfence Intelligence

Actions

  1. Confirm the installed plugin is latepoint and note its exact version.
  2. Back up and test compatibility, then update to 5.7.7 or a newer patched release; the current release is 5.7.8.
  3. Check password reset, login and booking flows after the update.
  4. Review unexpected password changes or customer access and preserve logs; the patch does not resolve a prior compromise.
  5. If the update cannot happen soon, have your provider assess a controlled restriction of the affected public customer flow and its business impact; this is not a guaranteed alternative fix.

Unknowns

  • Whether any customer or linked WordPress account was taken over before patching; only a log and account review can tell you.
  • Whether wp_users_as_customers is enabled on your site, which decides if linked WordPress accounts are also in scope.

Sources

  • Wordfence Intelligence · retrieved https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/latepoint-2/appointment-booking-plugin-576-unauthenticated-authentication-bypass-via-account-takeover-via-is-not-null-sentinel-in-password-reset-token-parameter
  • LatePoint / WordPress Plugin Repository · retrieved https://plugins.svn.wordpress.org/latepoint/trunk/readme.txt
  • LatePoint · retrieved https://latepoint.com/changelog/

Change history

  1. — Published: Published 7 November 2026 from the Wordfence advisory of 6 November 2026 and the vendor changelog.
  2. — Updated: 17 November 2026: Exploitation status updated after Wordfence reported blocking 1,635 attack attempts in the 24 hours preceding its report, as observed on 17 November. Aggregate blocked attempts only; no successful compromise confirmed in the reviewed sources. Advisory date of 6 November, affected versions, patched releases, and recommended actions are unchanged. This is new telemetry on the existing advisory, not a new vulnerability.

Subscribe: RSS feed · JSON Feed · Feed format and fields