CVE-2026-17538 latepoint CVE debrief

Who should care

Defenders responsible for WordPress installations with the LatePoint plugin should assess exposure and prioritize verification and remediation efforts. This includes reviewing compensating controls for exposed systems while remediation is scheduled and verified, and tracking exceptions and retesting remediated assets.

Why it matters

Authenticated attackers with Subscriber-level access can modify personal information of arbitrary LatePoint customers, potentially leading to account takeover.

• Modification of arbitrary customer personal information (first name, last name, email, phone, notes).
• Potential account takeover via password reset when the contact_merge setting is 'phone'.

Technical summary

The LatePoint - Appointment Booking & Reservation plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 5.6.9. This is due to the process_step_customer() function using is_user_logged_in() as the sole gate before merging POSTed customer data into an existing LatePoint customer, without any ownership checks. The vulnerability enables authenticated attackers with Subscriber-level access to modify the personal information (first name, last name, email, phone, notes) of arbitrary LatePoint customers, and, when the contact_merge setting is 'phone', to overwrite the victim's email address and take over the account via a password reset.

Defensive priority

Defenders should prioritize verifying and updating to a patched version of the plugin, if available, and restrict access to sensitive customer information.

Recommended defensive actions

• Verify and update to a patched version of the plugin, if available.
• Restrict access to sensitive customer information.
• Monitor for suspicious activity related to customer data modifications.
• 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 vulnerability exists in versions up to and including 5.6.9 of the LatePoint plugin due to insufficient ownership checks in the process_step_customer() function. This function uses is_user_logged_in() as the sole gate before merging POSTed customer data into an existing LatePoint customer, without any ownership checks. Defenders should verify the presence of affected product deployments in managed environments and assess exposure. The CVE record was published on 2026-10-07T23:27:12.424Z and has not been modified since then.

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.