CVE-2023-24407 is a medium severity missing authorization flaw (CVSS 5.0) in the Booking calendar, Appointment Booking System WordPress plugin, affecting every version through 3.2.3. We could not confirm a fixed version, so check the plugin page for a release newer than 3.2.3. Check every site you run, because plugin copies on forgotten staging sites are easy to miss.
What's affected
- Booking calendar, Appointment Booking System plugin, all versions up to and including 3.2.3, per the record and the Patchstack listing.
- Fixed version: we could not confirm one, so check the plugin page for a release newer than 3.2.3.
- Severity: CVSS 3.1 score 5.0 Medium, vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L.
Patchstack returned an access denied response to our fetch, so the fixed version is not confirmed here.
How to check if you're exposed
If you manage the site with WP-CLI, list the plugin and its version:
wp plugin list --fields=name,version,status | grep -i booking-calendar
The plugin directory slug is booking-calendar. Without WP-CLI, open Plugins, Installed Plugins in the WordPress admin and read the version under the Booking calendar, Appointment Booking System entry. Check every site you run, including staging copies and sites that sit behind a hosting dashboard you rarely open. Multisite networks should also check each subsite, because a plugin can be active on one and absent on another.
What to do now
- Find every WordPress site that has Booking calendar, Appointment Booking System installed, including staging copies, and read the version.
- Look for a newer release on the plugin page. If none exists, deactivate the plugin or replace it with a maintained alternative.
- If you cannot update right away, deactivate the plugin until you can.
- Review web server logs for unexpected requests to the plugin around the time you learned of the issue.
Why it matters
The weakness is missing authorization (CWE-862 (Missing Authorization)). Broken access control means a function runs without checking that the caller is allowed to use it. WordPress plugins register many actions that requests can reach, so each one needs an explicit capability check. When the check is missing, the plugin trusts the request, whatever role the requester holds.
The vector requires a low privilege account and a high attack complexity, with low impact on confidentiality, integrity and availability. That gives a Medium 5.0. The same plugin carries CVE-2023-24373 for the same version range, so one update should address both once a fixed release is confirmed. CISA has not listed this CVE in its Known Exploited Vulnerabilities catalog, according to the record we hold, and none of the pages we read said it is being exploited.
Plugin flaws are a supply chain problem as much as a coding problem. A WordPress site often runs dozens of third party plugins, each maintained by a different team, and each with its own release schedule. The practical defence is an inventory you trust and a habit of applying updates promptly.
Quick check
Do both CVEs for this plugin share a fix?
They share the version range, through 3.2.3. We could not confirm the fixed version, so check the plugin page for a release newer than 3.2.3.
What if the plugin has no update?
Replace it with a maintained booking plugin, and remove the old one rather than only deactivating it.
Sources
Last reviewed: 19 October 2026.