WordPress security changelog
MEDIUM CVE-2026-12433 Deferred

Hydra Booking — Appointment Scheduling & Booking Calendar: A security weakness

Hydra Booking — Appointment Scheduling & Booking Calendar is affected by a security weakness. Exploitation requires an authenticated WordPress account. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 1.2.1.

CVE / CNA score 4.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Hydra Booking — Appointment Scheduling & Booking Calendar
Plugin slug
hydra-booking
Affected
<= 1.2.1
Safe version
> 1.2.1
Published
Jul 09, 2026
Weakness
CWE-639 — Authorization Bypass Through User-Controlled Key

This CVE was published Jul 09, 2026 and is one of 10 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Hydra Booking — Appointment Scheduling & Booking Calendar to a release after 1.2.1, or disable and remove it until a fixed version is available.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Hydra Booking – Appointment Scheduling & Booking Calendar plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 1.2.1 via the /wp-json/hydra-booking/v1/booking/details/{id} REST endpoint. This is due to the getBookingDetails() callback only enforcing the tfhb_manage_options capability via tfhb_manage_options_permission(), without verifying that the requested booking belongs to the currently authenticated host (the lookup in getBookingDetailsData() filters solely on the booking id supplied in the URL). This makes it possible for authenticated attackers, with Hydra Host-level access and above (a role created by the plugin which grants tfhb_manage_options), to view sensitive booking records belonging to other hosts, including attendee names, emails, phone numbers, addresses, meeting details, payment method and status, transaction history, and internal notes by iterating booking IDs.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

References

Primary and upstream sources