CVE-2026-1537

LatePoint – Calendar Booking Plugin for Appointments and Events <= 5.2.6 - Missing Authorization to Booking Details Exposure

Strategic Overview

Status
Patched in 5.2.7
Affected Version
<= 5.2.6
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-1537
View all Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress vulnerabilities

At a glance

CVE-2026-1537 is a medium-severity Missing Authorization vulnerability in the Appointment Booking Plugin WordPress plugin, affecting versions <= 5.2.6. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.2.7; sites on affected versions should update now. Disclosed February 2026, reported by Chiao-Lin Yu (Steven Meow).

Vulnerability Overview

The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the load_step() function in all versions up to, and including, 5.2.6. This makes it possible for unauthenticated attackers to view booking information including customer names, email addresses, phone numbers, appointment times, and service details.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Appointment Booking Plugin <= 5.2.6 carries this weakness at load_step(), and reaching it takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Appointment Booking Plugin the fix is 5.2.7: builds <= 5.2.6 are affected, anything from 5.2.7 onward is not.

Remediation

Update to version 5.2.7, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Appointment Booking Plugin 5.2.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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