LatePoint <= 5.6.1 - Missing Authorization to Unauthenticated Arbitrary Customer Data Modification via process_step_customer() Booking Form Customer Step
The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 5.6.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to modify the personally identifiable information (first name, last name, phone number, and notes) of any existing customer record, including those linked to administrator accounts, by submitting the booking form with a known customer's email address. Exploitation requires the plugin to be configured with guest bookings enabled (is_customer_auth_disabled() returning true), which is necessary for the vulnerable unauthenticated code path in process_step_customer() to be reached.
Quick answer
Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- *-5.6.1
Fixed versions
- 5.6.2
How to fix it
Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress is affected by CVE-2026-11398, a authorization bypass issue in versions *-5.6.1. Prioritize exposed production sites and users with elevated permissions first. The recommended remediation is to update to version 5.6.2 or a newer vendor-supported patched release. If immediate patching is not possible, reduce exposure, restrict access to the vulnerable workflow, and monitor logs until the vendor-supported fix is in place.
- Inventory every WordPress site that uses Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress, including production, staging, multisite, customer, and managed environments.
- Confirm the installed plugin or theme version and compare it with versions *-5.6.1 from the linked advisory.
- Apply the remediation: update to version 5.6.2 or a newer vendor-supported patched release.
- If the update cannot be applied immediately, disable Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress, remove unused roles that can reach the vulnerable feature, and restrict the affected admin, REST, shortcode, upload, comment, booking, or ecommerce workflow.
- Review application, web server, security plugin, WAF, authentication, and administrator activity logs for attempts related to CVE-2026-11398.
- Rotate administrator sessions, API keys, webhook secrets, database credentials, and integration tokens if logs or file/content review suggest compromise.
- Clear application, object, page, CDN, and browser caches after remediation so vulnerable assets, stored payloads, or stale responses are not served.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress is no longer running versions *-5.6.1 and record the patched or mitigated version in the remediation ticket.
- Verify unauthenticated, subscriber, contributor, author, shop manager, donor, booking, or custom-role users can no longer trigger the affected action.
- Review logs before and after the fix for exploitation attempts, unexpected content changes, suspicious admin actions, or database/file access.
- Rerun a Fixnx scan and any relevant plugin, WAF, or manual regression checks to confirm public exposure is reduced.
- Document the advisory link, affected assets, remediation action, verification evidence, and any cleanup or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-11398?
Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress versions listed as affected should be reviewed: *-5.6.1.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.