Appointment Hour Booking at a glance
- 16 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Sep 30, 2026.
- Ranked #1653 by popularity on WordPress.org (10,000+ active installs).
- The latest version is 1.6.07 (released Nov 16, 2026). The most recent security fix shipped in 1.5.98.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Appointment Hour Booking version
Enter the Appointment Hour Booking version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Appointment Hour Booking”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Appointment Hour Booking”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (1.6.07). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Appointment Hour Booking vulnerabilities
Appointment Hour Booking <= 1.5.97 - Unauthenticated Stored DOM-Based Cross-Site Scripting via Booking Form Single-Line Field via Schedule Calendar List Renderer
Cross-site scripting (XSS) · CVE-2026-96573
Affected versions: ≤ 1.5.97
Fixed in: 1.5.98
Severity: High 7.2 · Disclosed Sep 30, 2026
Appointment Hour Booking <= 1.5.94 - Unauthenticated Appointment Slot Capacity Bypass
Other weakness · CVE-2026-86475
Affected versions: ≤ 1.5.94
Fixed in: 1.5.95
Severity: Medium 5.3 · Disclosed Sep 14, 2026
Appointment Hour Booking – Booking Calendar <= 1.5.94 - Missing Authorization
Missing authorization · CVE-2026-66679
Affected versions: ≤ 1.5.94
Fixed in: 1.5.95
Severity: Medium 5.3 · Disclosed Aug 18, 2026
Appointment Hour Booking <= 1.5.87 - Unauthenticated Price Manipulation
Other weakness · CVE-2026-16282
Affected versions: ≤ 1.5.87
Fixed in: 1.5.88
Severity: Medium 5.3 · Disclosed Aug 3, 2026
Appointment Hour Booking – Booking Calendar <= 1.5.86 - Authenticated (Contributor+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2026-65514
Affected versions: ≤ 1.5.86
Fixed in: 1.5.87
Severity: Medium 6.4 · Disclosed Jul 23, 2026
Appointment Hour Booking – Booking Calendar <= 1.5.60 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'Min/Max Length' Field Configuration
Cross-site scripting (XSS) · CVE-2026-1083
Affected versions: ≤ 1.5.60
Fixed in: 1.5.61
Severity: Medium 4.4 · Disclosed Jan 27, 2026
Appointment Hour Booking <= 1.4.56 - Captcha Bypass
Other weakness · CVE-2024-32720
Affected versions: ≤ 1.4.56
Fixed in: 1.4.57
Severity: Medium 5.3 · Disclosed Apr 22, 2024
Appointment Hour Booking <= 1.4.23 - Missing Authorization to Double Booking
Missing authorization · CVE-2023-45649
Affected versions: ≤ 1.4.23
Fixed in: 1.4.24
Severity: Medium 5.3 · Disclosed Oct 11, 2023
Appointment Hour Booking <= 1.3.72 - Unauthenticated iFrame Injection via Appointment Form
Other weakness · CVE-2022-4035
Affected versions: ≤ 1.3.72
Fixed in: 1.3.73
Severity: High 7.2 · Disclosed Nov 29, 2022
Appointment Hour Booking <= 1.3.72 - CSV Injection
Other weakness · CVE-2022-4034
Affected versions: ≤ 1.3.72
Fixed in: 1.3.73
Severity: Medium 5.8 · Disclosed Nov 29, 2022
Appointment Hour Booking <= 1.3.72 - CAPTCHA Bypass
Other weakness · CVE-2022-4036
Affected versions: ≤ 1.3.72
Fixed in: 1.3.73
Severity: Medium 5.3 · Disclosed Nov 29, 2022
Appointment Hour Booking <= 1.3.71 - Missing Authorization
Missing authorization · CVE-2022-41692
Affected versions: ≤ 1.3.71
Fixed in: 1.3.72
Severity: Medium 4.3 · Disclosed Oct 30, 2022
Appointment Hour Booking <= 1.3.55 - Authenticated Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2022-1710
Affected versions: ≤ 1.3.55
Fixed in: 1.3.56
Severity: Medium 4.8 · Disclosed May 23, 2022
Appointment Hour Booking <= 1.3.16 - Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2021-24712
Affected versions: < 1.3.17
Fixed in: 1.3.17
Severity: Medium 6.4 · Disclosed Sep 10, 2021
Appointment Hour Booking <= 1.3.15 Admin+ Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2021-24673
Affected versions: < 1.3.16
Fixed in: 1.3.16
Severity: Medium 5.5 · Disclosed Sep 6, 2021
Appointment Hour Booking – WordPress Booking Plugin <= 1.1.45 - Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2019-13505
Affected versions: < 1.1.46
Fixed in: 1.1.46
Severity: Medium 6.1 · Disclosed Jul 9, 2019
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Appointment Hour Booking <= 1.5.97 - Unauthenticated Stored DOM-Based Cross-Site Scripting via Booking Form Single-Line Field via Schedule Calendar List RendererCross-site scripting (XSS) · CVE-2026-96573 | ≤ 1.5.97 | 1.5.98 | High 7.2 | Sep 30, 2026 |
| Appointment Hour Booking <= 1.5.94 - Unauthenticated Appointment Slot Capacity BypassOther weakness · CVE-2026-86475 | ≤ 1.5.94 | 1.5.95 | Medium 5.3 | Sep 14, 2026 |
| Appointment Hour Booking – Booking Calendar <= 1.5.94 - Missing AuthorizationMissing authorization · CVE-2026-66679 | ≤ 1.5.94 | 1.5.95 | Medium 5.3 | Aug 18, 2026 |
| Appointment Hour Booking <= 1.5.87 - Unauthenticated Price ManipulationOther weakness · CVE-2026-16282 | ≤ 1.5.87 | 1.5.88 | Medium 5.3 | Aug 3, 2026 |
| Appointment Hour Booking – Booking Calendar <= 1.5.86 - Authenticated (Contributor+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2026-65514 | ≤ 1.5.86 | 1.5.87 | Medium 6.4 | Jul 23, 2026 |
| Appointment Hour Booking – Booking Calendar <= 1.5.60 - Authenticated (Administrator+) Stored Cross-Site Scripting via 'Min/Max Length' Field ConfigurationCross-site scripting (XSS) · CVE-2026-1083 | ≤ 1.5.60 | 1.5.61 | Medium 4.4 | Jan 27, 2026 |
| Appointment Hour Booking <= 1.4.56 - Captcha BypassOther weakness · CVE-2024-32720 | ≤ 1.4.56 | 1.4.57 | Medium 5.3 | Apr 22, 2024 |
| Appointment Hour Booking <= 1.4.23 - Missing Authorization to Double BookingMissing authorization · CVE-2023-45649 | ≤ 1.4.23 | 1.4.24 | Medium 5.3 | Oct 11, 2023 |
| Appointment Hour Booking <= 1.3.72 - Unauthenticated iFrame Injection via Appointment FormOther weakness · CVE-2022-4035 | ≤ 1.3.72 | 1.3.73 | High 7.2 | Nov 29, 2022 |
| Appointment Hour Booking <= 1.3.72 - CSV InjectionOther weakness · CVE-2022-4034 | ≤ 1.3.72 | 1.3.73 | Medium 5.8 | Nov 29, 2022 |
| Appointment Hour Booking <= 1.3.72 - CAPTCHA BypassOther weakness · CVE-2022-4036 | ≤ 1.3.72 | 1.3.73 | Medium 5.3 | Nov 29, 2022 |
| Appointment Hour Booking <= 1.3.71 - Missing AuthorizationMissing authorization · CVE-2022-41692 | ≤ 1.3.71 | 1.3.72 | Medium 4.3 | Oct 30, 2022 |
| Appointment Hour Booking <= 1.3.55 - Authenticated Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2022-1710 | ≤ 1.3.55 | 1.3.56 | Medium 4.8 | May 23, 2022 |
| Appointment Hour Booking <= 1.3.16 - Cross-Site ScriptingCross-site scripting (XSS) · CVE-2021-24712 | < 1.3.17 | 1.3.17 | Medium 6.4 | Sep 10, 2021 |
| Appointment Hour Booking <= 1.3.15 Admin+ Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2021-24673 | < 1.3.16 | 1.3.16 | Medium 5.5 | Sep 6, 2021 |
| Appointment Hour Booking – WordPress Booking Plugin <= 1.1.45 - Cross-Site ScriptingCross-site scripting (XSS) · CVE-2019-13505 | < 1.1.46 | 1.1.46 | Medium 6.1 | Jul 9, 2019 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Sep 30, 2026.
Most common weaknesses in Appointment Hour Booking
Cross-site scripting (XSS)
7 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Missing authorization
3 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Frequently asked questions
Is Appointment Hour Booking safe to use?
Appointment Hour Booking is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (1.6.07) and turn on automatic updates.
How do I find which version of Appointment Hour Booking my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesAppointment Hour Booking on WordPress.org