Simply Schedule Appointments · Security record
Is Simply Schedule Appointments safe?
No known vulnerability affects the current version (1.6.13.0). 51 issues were found in earlier versions and fixed, the latest disclosed on Oct 15, 2026.
Checked 3 days ago against the WPVulnerability database, for version 1.6.13.0.
How it’s looked after
- Last release
- Nov 3, 2026 (5 days ago)
- Releases in the last year
- 43
- Tested up to
- WordPress 7.1.4
- Support resolved
- 6 of 6 threads in two months
- Active installs
- 50K+
51 known vulnerabilities
- 2 critical
- 17 high
- 24 medium
- 8 not rated
None affects the current version.
Disclosed each year
- 20222
- 20231
- 20248
- 20254
- 202636
Every known vulnerability in Simply Schedule Appointments
Newest first, with any that affect the current version at the top.
Fixed in 1.6.12.37 · CVE-2026-110382 · Oct 15, 2026 · Wordfence
Fixed in 1.6.12.37 · CVE-2026-110381 · Oct 15, 2026 · Wordfence
Fixed in 1.6.12.37 · CVE-2026-104000 · Oct 9, 2026 · Wordfence
- medium
Incorrect Authorization to Unauthenticated Sensitive Field Modification via Appointment Public Token
Fixed in 1.6.12.0 · CVE-2026-6723 · Sep 30, 2026 · Wordfence
Fixed in 1.6.12.33 · CVE-2026-94673 · Sep 30, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 1.6.12.31 · CVE-2026-94074 · Sep 30, 2026 · Wordfence
Fixed in 1.6.12.33 · CVE-2026-91109 · Sep 30, 2026 · Wordfence
Fixed in 1.6.12.33 · CVE-2026-92245 · Sep 30, 2026 · Wordfence
Fixed in 1.6.12.33 · CVE-2026-89294 · Sep 2, 2026 · Wordfence
Fixed in 1.6.12.24 · CVE-2026-84764 · Aug 15, 2026 · Wordfence
Fixed in 1.6.12.17 · CVE-2026-16541 · Aug 15, 2026 · CVE
- medium
Authenticated (Contributor+) Insecure Direct Object Reference to Sensitive Information Exposure
Fixed in 1.6.12.11 · CVE-2026-13358 · Aug 15, 2026 · Wordfence
Fixed in 1.6.12.11 · CVE-2026-15254 · Aug 3, 2026 · CVE
Fixed in 1.6.12.6 · CVE-2026-16540 · Aug 2, 2026 · Wordfence
- critical
Unauthenticated SQL Injection
Fixed in 1.6.12.11 · CVE-2026-65508 · Jul 28, 2026 · Wordfence
Fixed in 1.6.12.11 · CVE-2026-65513 · Jul 28, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 1.6.12.0 · CVE-2026-59523 · Jul 9, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 1.6.12.6 · CVE-2026-57812 · Jul 9, 2026 · Wordfence
Fixed in 1.6.12.4 · CVE-2026-13400 · Jul 6, 2026 · Wordfence
Fixed in 1.6.12.4 · CVE-2026-57317 · Jun 26, 2026 · Wordfence
Fixed in 1.6.11.0 · CVE-2026-39447 · May 28, 2026 · Wordfence
Fixed in 1.6.11.9 · CVE-2026-6937 · May 27, 2026 · Wordfence
Fixed in 1.6.11.9 · CVE-2026-7797 · May 27, 2026 · Wordfence
Fixed in 1.6.11.7 · CVE-2026-7493 · May 26, 2026 · Wordfence
Fixed in 1.6.11 · CVE-2026-4807 · May 6, 2026 · Wordfence
Fixed in 1.6.11.2 · CVE-2026-42384 · Apr 27, 2026 · Wordfence
- critical
Unauthenticated SQL Injection
Fixed in 1.6.9.29 · CVE-2026-39493 · Apr 8, 2026 · Wordfence
Fixed in 1.6.9.29 · CVE-2026-39495 · Mar 26, 2026 · Wordfence
Fixed in 1.6.10.2 · CVE-2026-3658 · Mar 18, 2026 · Wordfence
Fixed in 1.6.10.0 · CVE-2026-1704 · Mar 12, 2026 · Wordfence
Fixed in 1.6.10.0 · CVE-2026-3045 · Mar 12, 2026 · Wordfence
Fixed in 1.6.9.29 · CVE-2026-1708 · Mar 10, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 1.6.11.1 · CVE-2026-39694 · Feb 26, 2026 · Wordfence
- medium
Missing Authorization
Fixed in 1.6.9.17 · CVE-2025-69315 · Jan 20, 2026 · Wordfence
Fixed in 1.6.9.13 · CVE-2025-12166 · Jan 14, 2026 · Wordfence
Fixed in 1.6.9.6 · CVE-2025-11723 · Jan 5, 2026 · Wordfence
Fixed in 1.6.9.17 · CVE-2025-13754 · Dec 18, 2025 · Wordfence
Fixed in 1.6.8.32 · CVE-2025-4667 · Jun 13, 2025 · Wordfence
Fixed in 1.6.8.7 · CVE-2025-1119 · Mar 12, 2025 · Wordfence
Fixed in 1.6.8.5 · CVE-2024-13431 · Mar 6, 2025 · Wordfence
Fixed in 1.6.7.55 · CVE-2024-7876 · Oct 15, 2024 · Wordfence
Fixed in 1.6.7.55 · CVE-2024-7877 · Oct 15, 2024 · Wordfence
Fixed in 1.6.7.43 · CVE-2024-7129 · Aug 23, 2024 · Wordfence
Fixed in 1.6.7.18 · CVE-2024-4288 · May 15, 2024 · Wordfence
Fixed in 1.6.6.24 · CVE-2024-22311 · Mar 26, 2024 · Wordfence
Fixed in 1.6.7.9 · CVE-2024-2341 · Mar 20, 2024 · Wordfence
Fixed in 1.6.7.9 · CVE-2024-2342 · Mar 20, 2024 · Wordfence
Fixed in 1.6.6.24 · CVE-2024-1760 · Mar 5, 2024 · Wordfence
Fixed in 1.6.6.1 · CVE-2023-50851 · Dec 21, 2023 · Wordfence
Fixed in 1.5.7.7 · CVE-2022-2373 · Aug 8, 2022 · Wordfence
Fixed in 1.5.7.7 · CVE-2022-2374 · Aug 8, 2022 · Wordfence
Questions about Simply Schedule Appointments’s security
Is Simply Schedule Appointments safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Simply Schedule Appointments updated: most attacks target sites that haven’t updated.
Does Simply Schedule Appointments have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 51 older issues, fixed in earlier versions, so keep Simply Schedule Appointments up to date.
Is Simply Schedule Appointments still maintained?
Yes. Its last release was 5 days ago. Its authors resolved 6 of the 6 support threads opened in the last two months.
Is Simply Schedule Appointments compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.