CVE-2026-105197

Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress < 5.6.5 - Authenticated (Custom Role+) Insecure Direct Object Reference

2026-10-08 00:00
Muni Nitish Kumar Yaddala

Strategic Overview

Status
Patched in 5.6.5
Affected Plugin
Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress
Affected Version
< 5.6.5
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-105197
View all Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress vulnerabilities

At a glance

CVE-2026-105197 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Appointment Booking Plugin WordPress plugin, affecting versions < 5.6.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Custom Role level or above. The issue is fixed in version 5.6.5; sites on affected versions should update now. Disclosed October 2026, reported by Muni Nitish Kumar Yaddala.

Vulnerability Overview

The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to 5.6.5. This is due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with custom role-level access and above, to perform an unauthorized action.

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 interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Appointment Booking Plugin < 5.6.5 takes an account at Custom Role level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Appointment Booking Plugin the fix is 5.6.5: builds < 5.6.5 are affected, anything from 5.6.5 onward is not.

Remediation

Update to version 5.6.5, 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.6.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-105197https://www.wordfence.com/threat-intel/vulnerabilities/id/69660595-0bd3-46d9-9802-856d1fe96f9fhttps://nvd.nist.gov/vuln/detail/CVE-2026-105197

Related records

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