CVE-2026-9719

LatePoint <= 5.6.0 - Cross-Site Request Forgery via invoices__change_status Action

2026-06-05 11:05
alex_henry20

Strategic Overview

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

At a glance

CVE-2026-9719 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Appointment Booking Plugin WordPress plugin, affecting versions <= 5.6.0. 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.6.1; sites on affected versions should update now. Disclosed June 2026, reported by alex_henry20.

Vulnerability Overview

The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.6.0. This is due to missing or incorrect nonce validation on the change_status function. This makes it possible for unauthenticated attackers to change the status of arbitrary invoices — including marking unpaid invoices as paid — without administrator consent via a forged request granted they can trick a site administrator 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)

Reaching this weakness in Appointment Booking Plugin <= 5.6.0 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.6.1: builds <= 5.6.0 are affected, anything from 5.6.1 onward is not.

Remediation

Update to version 5.6.1, 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.6.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-9719https://www.wordfence.com/threat-intel/vulnerabilities/id/c720fffe-c089-450a-ac5f-1138c1c223d9https://nvd.nist.gov/vuln/detail/CVE-2026-9719

Related records

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