Quick answers
- Is CVE-2026-11866 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11866 being exploited in the wild.
- How severe is CVE-2026-11866?
- Informational severity, with a CVSS score of 5.4, published 16 July 2026.
- Which products and versions are affected?
- LatePoint < 5.6.3.
- Is there a fix for CVE-2026-11866?
- A patch was published on 2026-06-25: Fix released in version 5.6.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-11866 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-11866?
- Check whether you run LatePoint at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The LatePoint plugin (versions prior to 5.6.3) fails to validate CSRF nonces on several state-changing actions handled by its central request dispatcher (`latepoint_route_call`). An unauthenticated attacker can exploit this by crafting a malicious webpage that, when visited by a logged-in administrator, triggers unauthorized requests to `admin-ajax.php`. Successful exploitation allows the attacker to perform privileged actions such as overwriting booking-form configurations, deactivating customer data fields, or disconnecting integrated payment gateways like Stripe. The vulnerability exists because the dispatcher accepts requests even when the `_wpnonce` parameter is missing or invalid. The issue is resolved in version 5.6.3.
Affected products
- LatePoint LatePoint Appointment Booking Plugin < 5.6.3
Timeline
- 2026-06-25: disclosed: Initial public disclosure by WPScan
- 2026-06-25: patched: Fix released in version 5.6.3
- 2026-07-16: advisory: NVD publication date