CVE-2026-111602

Appointment Booking Plugin <= 5.7.4 - Unauthenticated Sensitive Information Disclosure via ORM Operator Injection in 'customer[uuid]' Parameter

2026-10-16 14:30
Jiří Fryjauf (jfryjauf)

Strategic Overview

Status
Patched in 5.7.5
Affected Plugin
Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress
Affected Version
<= 5.7.4
CVSS
3.7Low
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-111602
View all Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress vulnerabilities

At a glance

CVE-2026-111602 is a low-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Appointment Booking Plugin WordPress plugin, affecting versions <= 5.7.4. It carries a CVSS score of 3.7 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 5.7.5; sites on affected versions should update now. Disclosed October 2026, reported by Jiří Fryjauf (jfryjauf).

Vulnerability Overview

The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.7.4 via the 'params (customer[uuid])' parameter. This makes it possible for unauthenticated attackers to extract the first name, last name, email address, phone number, and notes of every customer record in the database by enumerating uuid prefixes via the unauthenticated steps__load_step AJAX endpoint. This vulnerability is only exploitable when the LatePoint plugin is configured with the 'Field used for authentication' setting set to 'Disable ability to login' (guest checkout mode).

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Appointment Booking Plugin <= 5.7.4 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Appointment Booking Plugin the fix is 5.7.5: builds <= 5.7.4 are affected, anything from 5.7.5 onward is not.

Remediation

Update to version 5.7.5, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Appointment Booking Plugin 5.7.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-111602https://www.wordfence.com/threat-intel/vulnerabilities/id/6afce24f-30cd-4aeb-a5dd-20bd80a75779https://nvd.nist.gov/vuln/detail/CVE-2026-111602

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C