CVE-2025-14873

LatePoint – Calendar Booking Plugin for Appointments and Events <= 5.2.5 - Cross-Site Request Forgery

2026-02-13 18:24
Moose Love

Strategic Overview

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

At a glance

CVE-2025-14873 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Appointment Booking Plugin WordPress plugin, affecting versions <= 5.2.5. 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.2.6; sites on affected versions should update now. Disclosed February 2026, reported by Moose Love.

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.2.5. This is due to the 'call_by_route_name' function in the routing layer only validating user capabilities without enforcing nonce verification. This makes it possible for unauthenticated attackers to perform multiple administrative actions via forged requests 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)

Appointment Booking Plugin <= 5.2.5 carries this weakness at call_by_route_name, 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.2.6: builds <= 5.2.5 are affected, anything from 5.2.6 onward is not.

Remediation

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-14873https://www.wordfence.com/threat-intel/vulnerabilities/id/1f7aa23c-ffa7-481b-8481-a36c7ed599d8https://nvd.nist.gov/vuln/detail/CVE-2025-14873

Related records

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