Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress vulnerabilities
Plugin slug latepoint · 59 known vulnerabilities · latest disclosed 2026-11-06 · WordPress.org page
2 vulnerabilities have no fixed version yet. If you use this plugin, consider disabling or replacing it until a fix is released.
23 of 59 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Critical 9.1 | <= 5.7.6 | 5.7.7 | CVE-2026-118066 | 2026-11-06 | Advisory |
| Medium 5.4 | <= 5.7.6 | 5.7.7 | CVE-2026-119152 | 2026-11-06 | Advisory |
| Medium 4.4 | <= 5.7.5 | 5.7.6 | CVE-2026-105258 | 2026-10-27 | Advisory |
| Medium 5.3 | <= 5.7.4 | 5.7.5 | CVE-2026-105256 | 2026-10-19 | Advisory |
| Medium 4.3 | <= 5.7.4 | 5.7.5 | CVE-2026-105257 | 2026-10-19 | Advisory |
| Low 3.7 | <= 5.7.4 | 5.7.5 | CVE-2026-111602 | 2026-10-16 | Advisory |
| Critical 9.1 | <= 5.7.4 | 5.7.5 | CVE-2026-110653 | 2026-10-16 | Advisory |
| High 7.4 | <= 5.7.2 | 5.7.3 | CVE-2026-100163 | 2026-10-13 | Advisory |
| High 7.5 | <= 5.7.3 | 5.7.4 | CVE-2026-103366 | 2026-10-13 | Advisory |
| Medium 4.3 | <= 5.7.3 | 5.7.4 | CVE-2026-103380 | 2026-10-13 | Advisory |
| High 7.5 | <= 5.7.2 | 5.7.3 | CVE-2026-96662 | 2026-10-09 | Advisory |
| High 8.8 | <= 5.7.3 | 5.7.4 | CVE-2026-104766 | 2026-10-09 | Advisory |
| Medium 4.3 | <= 5.7.2 | 5.7.3 | CVE-2026-91050 | 2026-10-09 | Advisory |
| Medium 4.3 | < 5.6.5 | 5.6.5 | CVE-2026-105197 | 2026-10-08 | Advisory |
| Medium 4.3 | < 5.6.9 | 5.6.9 | CVE-2026-105196 | 2026-10-08 | Advisory |
| Medium 5.3 | < 5.7.3 | 5.7.3 | CVE-2026-105198 | 2026-10-08 | Advisory |
| Medium 5.4 | <= 5.6.9 | 5.6.10 | CVE-2026-17538 | 2026-10-07 | Advisory |
| Medium 5.3 | <= 5.7.1 | 5.7.2 | CVE-2026-94432 | 2026-10-01 | Advisory |
| Critical 9.1 | <= 5.7.0 | 5.7.1 | CVE-2026-92966 | 2026-09-30 | Advisory |
| Medium 4.3 | <= 5.6.3 | 5.6.4 | CVE-2026-13471 | 2026-09-17 | Advisory |
| Medium 4.3 | <= 5.6.9 | 5.6.10 | CVE-2026-18441 | 2026-09-17 | Advisory |
| Medium 6.4 | <= 5.3.2 | 5.4.0 | CVE-2026-5391 | 2026-08-05 | Advisory |
| Medium 5.3 | <= 5.6.7 | 5.6.8 | CVE-2026-15250 | 2026-07-10 | Advisory |
| High 7.5 | <= 5.6.3 | 5.6.4 | CVE-2026-57714 | 2026-07-08 | Advisory |
| High 7.5 | <= 5.4.0 | 5.4.1 | CVE-2026-5356 | 2026-07-07 | Advisory |
| Medium 5.3 | <= 5.6.1 | 5.6.2 | CVE-2026-11398 | 2026-07-02 | Advisory |
| Medium 5.3 | <= 5.6.2 | 5.6.3 | CVE-2026-12657 | 2026-07-01 | Advisory |
| High 8.8 | <= 5.6.3 | 5.6.4 | CVE-2026-13228 | 2026-06-30 | Advisory |
| Medium 4.3 | <= 5.6.2 | 5.6.3 | CVE-2026-11866 | 2026-06-25 | Advisory |
| High 7.5 | <= 5.5.1 | 5.5.2 | CVE-2026-8176 | 2026-06-15 | Advisory |
| Medium 4.3 | <= 5.6.0 | 5.6.1 | CVE-2026-9719 | 2026-06-05 | Advisory |
| High 8.8 | <= 5.5.1 | 5.5.2 | CVE-2026-49083 | 2026-06-05 | Advisory |
| Medium 4.3 | <= 5.3.2 | 5.4.0 | CVE-2026-5365 | 2026-05-13 | Advisory |
| Medium 5.3 | <= 5.5.0 | 5.5.1 | CVE-2026-7652 | 2026-05-08 | Advisory |
| High 7.2 | <= 5.5.0 | 5.5.1 | CVE-2026-7448 | 2026-05-06 | Advisory |
| High 7.2 | <= 5.5.0 | 5.5.1 | CVE-2026-7332 | 2026-05-05 | Advisory |
| Medium 6.4 | <= 5.5.0 | 5.5.1 | CVE-2026-7457 | 2026-05-05 | Advisory |
| High 8.8 | <= 5.4.1 | 5.4.2 | CVE-2026-6741 | 2026-04-27 | Advisory |
| Medium 5.3 | <= 5.3.2 | 5.4.0 | CVE-2026-5234 | 2026-04-16 | Advisory |
| Medium 6.4 | <= 5.3.0 | 5.3.1 | CVE-2026-4785 | 2026-04-07 | Advisory |
| Medium 4.3 | <= 5.2.6 | 5.2.7 | CVE-2026-32533 | 2026-03-23 | Advisory |
| Medium 6.1 | <= 5.2.7 | 5.2.8 | CVE-2026-2324 | 2026-03-10 | Advisory |
| Medium 6.5 | <= 5.2.7 | 5.2.8 | CVE-2026-1487 | 2026-03-02 | Advisory |
| High 8.8 | <= 5.2.7 | 5.2.8 | CVE-2026-1566 | 2026-03-02 | Advisory |
| Medium 4.3 | <= 5.2.5 | 5.2.6 | CVE-2025-14873 | 2026-02-13 | Advisory |
| Medium 5.3 | <= 5.2.6 | 5.2.7 | CVE-2026-1537 | 2026-02-11 | Advisory |
| High 7.2 | <= 5.2.5 | 5.2.6 | CVE-2026-0617 | 2026-02-02 | Advisory |
| Medium 6.4 | <= 5.1.94 | 5.2.0 | CVE-2025-6941 | 2025-09-29 | Advisory |
| High 8.2 | <= 5.1.94 | 5.2.0 | CVE-2025-7038 | 2025-09-29 | Advisory |
| High 8.8 | <= 5.1.94 | 5.2.0 | CVE-2025-7052 | 2025-09-29 | Advisory |
| Medium 5.5 | <= 5.1.94 | 5.2.0 | CVE-2025-6815 | 2025-09-29 | Advisory |
| Critical 9.8 | <= 5.1.93 | 5.1.94 | CVE-2025-6715 | 2025-07-23 | Advisory |
| Medium 5.3 | <= 5.1.92 | 5.1.93 | CVE-2025-3769 | 2025-05-13 | Advisory |
| Medium 6.4 | <= 5.1.6 | 5.1.7 | CVE-2025-30836 | 2025-03-27 | Advisory |
| Critical 9.8 | <= 5.0.12 | 5.0.13 | CVE-2024-8943 | 2024-09-24 | Advisory |
| Critical 9.8 | <= 5.0.11 | 5.0.12 | CVE-2024-8911 | 2024-09-20 | Advisory |
| Medium 6.4 | <= 4.9.91 | No fix yet | CVE-2024-43992 | 2024-08-29 | Advisory |
| Medium 4.3 | <= 4.9.91 | No fix yet | CVE-2024-43945 | 2024-08-26 | Advisory |
| Critical 9.1 | <= 4.9.9 | 4.9.9.1 | CVE-2024-2472 | 2024-06-13 | Advisory |
Check if a site is affected
Enter a site address to see which version of Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin safe to use?
2 known issue(s) have no fix yet, so check the table above before using it.
How do I check which version of Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.
Check any WordPress site in one click while you browse: Add PluginPeek to Chrome