CVE-2026-103380

Appointment Booking Plugin <= 5.7.3 - Authenticated (Subscriber+) Sensitive Information Exposure in 'first_name' Parameter Template Re-expansion

2026-10-13 19:18
walid213

Strategic Overview

Status
Patched in 5.7.4
Affected Version
<= 5.7.3
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-103380
View all Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress vulnerabilities

At a glance

CVE-2026-103380 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Appointment Booking Plugin WordPress plugin, affecting versions <= 5.7.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.7.4; sites on affected versions should update now. Disclosed October 2026, reported by walid213.

Vulnerability Overview

The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.7.3 via the 'params[customer][first_name]' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract privileged booking data including the administrator-only admin_notes field, assigned agent internal contact details, transaction tokens, and payment request URLs delivered via rendered notification emails. A LatePoint customer can exploit this by storing a template placeholder such as {{customer_admin_notes}} in their own first_name field via the customer_cabinet__update route, then triggering the password-reset email flow to receive the expanded value in the resulting notification.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Appointment Booking Plugin <= 5.7.3 carries this weakness at params[customer][first_name], and reaching it takes an account at Subscriber level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Appointment Booking Plugin the fix is 5.7.4: builds <= 5.7.3 are affected, anything from 5.7.4 onward is not.

Remediation

Update to version 5.7.4, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Appointment Booking Plugin 5.7.4 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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