CVE-2026-5365

LatePoint <= 5.3.2 - Cross-Site Request Forgery via 'customer_cabinet__request_cancellation' AJAX Route

2026-05-13 17:41
Tulgaaaa

Strategic Overview

Status
Patched in 5.4.0
Affected Version
<= 5.3.2
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-5365
View all Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress vulnerabilities

At a glance

CVE-2026-5365 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Appointment Booking Plugin WordPress plugin, affecting versions <= 5.3.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.4.0; sites on affected versions should update now. Disclosed May 2026, reported by Tulgaaaa.

Vulnerability Overview

The LatePoint plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to and including 5.3.2. This is due to missing nonce verification on the request_cancellation() function. This makes it possible for unauthenticated attackers to cancel a logged-in customer's bookings via a forged request, granted they can trick the customer into performing an action such as clicking on a link.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

Appointment Booking Plugin <= 5.3.2 carries this weakness at request_cancellation(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Appointment Booking Plugin the fix is 5.4.0: builds <= 5.3.2 are affected, anything from 5.4.0 onward is not.

Remediation

Update to version 5.4.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Appointment Booking Plugin: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Appointment Booking Plugin 5.4.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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