Simply Schedule Appointments vulnerabilities
Plugin slug simply-schedule-appointments · 52 known vulnerabilities · latest disclosed 2026-11-11 · WordPress.org page
Every listed vulnerability has a fix. Version 1.6.13.4 or later is not affected by any of them. If your site runs an older version, update it.
19 of 52 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Simply Schedule Appointments
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Medium 5.3 | <= 1.6.13.0 | 1.6.13.4 | CVE-2026-125437 | 2026-11-11 | Advisory |
| High 7.2 | <= 1.6.12.35 | 1.6.12.37 | CVE-2026-110382 | 2026-10-16 | Advisory |
| Medium 4.3 | <= 1.6.12.35 | 1.6.12.37 | CVE-2026-110381 | 2026-10-15 | Advisory |
| High 7.2 | <= 1.6.12.35 | 1.6.12.37 | CVE-2026-104000 | 2026-10-15 | Advisory |
| Medium 5.3 | <= 1.6.11.11 | 1.6.12.0 | CVE-2026-6723 | 2026-10-09 | Advisory |
| Medium 6.5 | <= 1.6.12.31 | 1.6.12.33 | CVE-2026-91109 | 2026-09-30 | Advisory |
| High 7.5 | <= 1.6.12.32 | 1.6.12.33 | CVE-2026-92245 | 2026-09-30 | Advisory |
| High 7.5 | <= 1.6.12.27 | 1.6.12.33 | CVE-2026-89294 | 2026-09-29 | Advisory |
| Medium 5.3 | <= 1.6.12.31 | 1.6.12.33 | CVE-2026-94673 | 2026-09-24 | Advisory |
| Medium 5.3 | <= 1.6.12.29 | 1.6.12.31 | CVE-2026-94074 | 2026-09-24 | Advisory |
| Medium 4.3 | <= 1.6.12.23 | 1.6.12.24 | CVE-2026-84764 | 2026-09-02 | Advisory |
| Medium 6.5 | <= 1.6.12.10 | 1.6.12.11 | CVE-2026-13358 | 2026-08-15 | Advisory |
| Medium 4.3 | <= 1.6.12.16 | 1.6.12.17 | CVE-2026-16541 | 2026-08-13 | Advisory |
| Medium 5.3 | < 1.6.12.6 | 1.6.12.6 | CVE-2026-16540 | 2026-08-06 | Advisory |
| High 7.5 | <= 1.6.12.10 | 1.6.12.11 | CVE-2026-65508 | 2026-07-28 | Advisory |
| High 7.2 | <= 1.6.12.10 | 1.6.12.11 | CVE-2026-65513 | 2026-07-28 | Advisory |
| Medium 4.3 | <= 1.6.12.10 | 1.6.12.11 | CVE-2026-15254 | 2026-07-23 | Advisory |
| Medium 5.3 | <= 1.6.12.4 | 1.6.12.6 | CVE-2026-57812 | 2026-07-09 | Advisory |
| Medium 5.3 | <= 1.6.11.11 | 1.6.12.0 | CVE-2026-59523 | 2026-07-09 | Advisory |
| High 7.2 | <= 1.6.12.3 | 1.6.12.4 | CVE-2026-13400 | 2026-07-06 | Advisory |
| High 7.2 | <= 1.6.12.2 | 1.6.12.4 | CVE-2026-57317 | 2026-06-26 | Advisory |
| High 7.2 | <= 1.6.10.6 | 1.6.11.0 | CVE-2026-39447 | 2026-05-28 | Advisory |
| Medium 5.3 | <= 1.6.11.8 | 1.6.11.9 | CVE-2026-6937 | 2026-05-27 | Advisory |
| High 7.5 | <= 1.6.11.8 | 1.6.11.9 | CVE-2026-7797 | 2026-05-27 | Advisory |
| Medium 5.3 | <= 1.6.11.5 | 1.6.11.7 | CVE-2026-7493 | 2026-05-26 | Advisory |
| Medium 6.5 | <= 1.6.10.6 | 1.6.11 | CVE-2026-4807 | 2026-05-06 | Advisory |
| Medium 5.3 | < 1.6.11.2 | 1.6.11.2 | CVE-2026-42384 | 2026-04-27 | Advisory |
| High 7.5 | <= 1.6.9.27 | 1.6.9.29 | CVE-2026-39493 | 2026-04-08 | Advisory |
| Medium 6.5 | <= 1.6.9.27 | 1.6.9.29 | CVE-2026-39495 | 2026-03-26 | Advisory |
| High 7.5 | <= 1.6.10.0 | 1.6.10.2 | CVE-2026-3658 | 2026-03-18 | Advisory |
| High 7.5 | <= 1.6.9.29 | 1.6.10.0 | CVE-2026-3045 | 2026-03-12 | Advisory |
| Medium 4.3 | <= 1.6.9.29 | 1.6.10.0 | CVE-2026-1704 | 2026-03-12 | Advisory |
| High 7.5 | <= 1.6.9.27 | 1.6.9.29 | CVE-2026-1708 | 2026-03-10 | Advisory |
| Medium 5.3 | <= 1.6.11.0 | 1.6.11.1 | CVE-2026-39694 | 2026-02-26 | Advisory |
| Medium 5.3 | <= 1.6.9.15 | 1.6.9.17 | CVE-2025-69315 | 2026-01-20 | Advisory |
| High 7.5 | <= 1.6.9.9 | 1.6.9.13 | CVE-2025-12166 | 2026-01-14 | Advisory |
| Medium 6.5 | <= 1.6.9.5 | 1.6.9.6 | CVE-2025-11723 | 2026-01-05 | Advisory |
| Medium 5.3 | <= 1.6.9.16 | 1.6.9.17 | CVE-2025-13754 | 2025-12-18 | Advisory |
| Medium 6.4 | <= 1.6.8.30 | 1.6.8.32 | CVE-2025-4667 | 2025-06-13 | Advisory |
| High 7.3 | <= 1.6.8.5 | 1.6.8.7 | CVE-2025-1119 | 2025-03-12 | Advisory |
| Medium 6.1 | <= 1.6.8.3 | 1.6.8.5 | CVE-2024-13431 | 2025-03-06 | Advisory |
| Medium 4.4 | <= 1.6.7.53 | 1.6.7.55 | CVE-2024-7877 | 2024-10-15 | Advisory |
| Medium 4.4 | <= 1.6.7.53 | 1.6.7.55 | CVE-2024-7876 | 2024-10-15 | Advisory |
| High 7.2 | <= 1.6.7.42 | 1.6.7.43 | CVE-2024-7129 | 2024-08-23 | Advisory |
| Medium 6.4 | <= 1.6.7.14 | 1.6.7.18 | CVE-2024-4288 | 2024-05-15 | Advisory |
| Medium 6.1 | <= 1.6.6.20 | 1.6.6.24 | CVE-2024-22311 | 2024-03-26 | Advisory |
| High 8.8 | <= 1.6.7.7 | 1.6.7.9 | CVE-2024-2342 | 2024-03-20 | Advisory |
| High 8.8 | <= 1.6.7.7 | 1.6.7.9 | CVE-2024-2341 | 2024-03-20 | Advisory |
| Medium 4.3 | <= 1.6.6.20 | 1.6.6.24 | CVE-2024-1760 | 2024-03-05 | Advisory |
| Medium 6.6 | < 1.6.6.1 | 1.6.6.1 | CVE-2023-50851 | 2023-12-21 | Advisory |
| Medium 5.5 | <= 1.5.7.5 | 1.5.7.7 | CVE-2022-2374 | 2022-08-08 | Advisory |
| Medium 5.3 | <= 1.5.7.5 | 1.5.7.7 | CVE-2022-2373 | 2022-08-08 | Advisory |
Check if a site is affected
Enter a site address to see which version of Simply Schedule Appointments and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Simply Schedule Appointments plugin safe to use?
All 52 known issues are fixed in current versions (1.6.13.4 or later). Keeping it updated is what matters.
How do I check which version of Simply Schedule Appointments 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