CVE-2026-12433 MEDIUM

CVE-2026-12433: Hydra Booking <= 1.2.1 - Authenticated (Custom+) Insecure Direct Object Reference to Sensitive Information Exposure via 'booking_id' Parameter

Vendor Themefic
Product Hydra Booking — Appointment Scheduling & Booking Calendar
Weakness CWE-639 · IDOR
Published July 9, 2026
Last update July 9, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity None

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Hydra Booking versions up to 1.2.1 contain an authorization flaw that allows authenticated users to access sensitive information they should not see. An attacker with a low-privilege account can read data belonging to other users or the system. The vulnerability requires login credentials but no additional user interaction. Update to a version newer than 1.2.1.

What an attacker can do

03Attacker Capabilities

Read sensitive data belonging to other users or the booking system.

Potential impact on your site

04Site Impact

Authenticated users can view confidential booking or customer information they shouldn't access.

Conditions required to exploit

05Prerequisites

Attacker must have a valid low-privilege account on the site.

Key dates

06Disclosure timeline

July 9, 2026 CVE published
July 9, 2026 Record updated

Related vulnerabilities

08Related CVE