CVE-2026-9719 MEDIUM

CVE-2026-9719: LatePoint <= 5.6.0 - Cross-Site Request Forgery via invoices__change_status Action

Vendor Latepoint
Product LatePoint – Calendar Booking Plugin for Appointments and Events
Weakness CWE-352 · CSRF
Published June 5, 2026
Last update June 6, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

LatePoint versions up to 5.6.0 contain a cross-site request forgery (CSRF) vulnerability. An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the booking plugin without their knowledge. The vulnerability requires the victim to visit the attacker's page while authenticated to the WordPress site.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on the booking plugin by tricking an authenticated admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

An attacker can modify booking settings, appointments, or plugin configuration if an admin visits a malicious link.

Conditions required to exploit

05Prerequisites

Victim must be logged into WordPress and visit an attacker-controlled page while authenticated.

Key dates

06Disclosure timeline

June 5, 2026 CVE published
June 6, 2026 Record updated

Related vulnerabilities

08Related CVE