Appointment Hour Booking · Security record
Is Appointment Hour Booking safe?
No known vulnerability affects the current version (1.6.04). 19 issues were found in earlier versions and fixed, the latest disclosed on Sep 14, 2026.
Checked 3 days ago against the WPVulnerability database, for version 1.6.04.
How it’s looked after
- Last release
- Nov 3, 2026 (5 days ago)
- Releases in the last year
- 55
- Tested up to
- WordPress 7.1.4
- Support resolved
- 4 of 4 threads in two months
- Active installs
- 10K+
19 known vulnerabilities
- 2 high
- 12 medium
- 5 not rated
None affects the current version.
Disclosed each year
- 20191
- 20212
- 20225
- 20231
- 20241
- 20266
Every known vulnerability in Appointment Hour Booking
Newest first, with any that affect the current version at the top.
Fixed in 1.5.98 · CVE-2026-96573 · Sep 14, 2026 · Wordfence
Fixed in 1.5.95 · CVE-2026-86475 · Aug 18, 2026 · Wordfence
Fixed in 1.5.88 · CVE-2026-16282 · Aug 8, 2026 · Patchstack
- medium
Missing Authorization
Fixed in 1.5.95 · CVE-2026-66679 · Aug 3, 2026 · Wordfence
Fixed in 1.5.87 · CVE-2026-65514 · Jul 23, 2026 · Wordfence
- medium
Authenticated (Administrator+) Stored Cross-Site Scripting via 'Min/Max Length' Field Configuration
Fixed in 1.5.61 · CVE-2026-1083 · Jan 27, 2026 · Wordfence
- medium
Captcha Bypass
Fixed in 1.4.57 · CVE-2024-32720 · Apr 22, 2024 · Wordfence
Fixed in 1.4.24 · CVE-2023-45649 · Oct 11, 2023 · Wordfence
- medium
CAPTCHA Bypass
Fixed in 1.3.73 · CVE-2022-4036 · Nov 29, 2022 · Wordfence
Fixed in 1.3.73 · CVE-2022-4035 · Nov 29, 2022 · Wordfence
- high
CSV Injection
Fixed in 1.3.73 · CVE-2022-4034 · Nov 29, 2022 · Wordfence
- medium
Missing Authorization
Fixed in 1.3.72 · CVE-2022-41692 · Oct 30, 2022 · Wordfence
Fixed in 1.3.56 · CVE-2022-1710 · May 23, 2022 · Wordfence
- medium
Cross-Site Scripting
Fixed in 1.3.17 · CVE-2021-24712 · Sep 10, 2021 · Wordfence
Fixed in 1.3.16 · CVE-2021-24673 · Sep 6, 2021 · Wordfence
- medium
Cross-Site Scripting
Fixed in 1.1.46 · CVE-2019-13505 · Jul 9, 2019 · Wordfence
Fixed in 1.3.73 · Patchstack
Fixed in 1.3.73 · Patchstack
Fixed in 1.3.73 · Patchstack
Questions about Appointment Hour Booking’s security
Is Appointment Hour Booking safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Appointment Hour Booking updated: most attacks target sites that haven’t updated.
Does Appointment Hour Booking have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 19 older issues, fixed in earlier versions, so keep Appointment Hour Booking up to date.
Is Appointment Hour Booking still maintained?
Yes. Its last release was 5 days ago. Its authors resolved 4 of the 4 support threads opened in the last two months.
Is Appointment Hour Booking 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.