CVE-2026-103380 latepoint CVE debrief

Who should care

Defenders responsible for WordPress installations with the Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress should assess exposure and prioritize verification and remediation efforts.

Why it matters

The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress vulnerability allows authenticated subscribers to access sensitive booking data, posing a risk to WordPress installations. Defenders should prioritize verification and remediation efforts.

• Potential exposure of privileged booking data
• Possible unauthorized access to administrator-only fields
• Risk of sensitive information disclosure to authenticated subscribers
• Need for verification and remediation of vulnerable plugin versions

Technical summary

The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin is vulnerable to Sensitive Information Exposure in versions up to and including 5.7.3. Authenticated attackers with subscriber-level access can exploit this by storing a template placeholder in their first_name field and triggering the password-reset email flow to receive expanded privileged booking data, including administrator-only admin_notes field, assigned agent internal contact details, transaction tokens, and payment request URLs.

Defensive priority

Defenders should prioritize verifying and updating to a patched version of the Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress, and monitor for suspicious activity related to authenticated subscribers.

Recommended defensive actions

• Verify and update to a patched version of the Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress
• Monitor for suspicious activity related to authenticated subscribers
• Review and restrict access to sensitive booking data
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability, including the affected versions and the potential impact. However, the corpus does not establish versions beyond 5.7.3, exploitation, impact, or remediation, which require verification from the supplied official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.