CVE-2026-12433
Last modified
CVE-2026-12433 is a medium-severity vulnerability rated 4.3/10 on the CVSS scale. 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). EPSS estimates a 0.43% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| themefic | Hydra Booking — Appointment Scheduling & Booking Calendar | <= 1.2.1 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-12433?
How severe is CVE-2026-12433?
How do I fix CVE-2026-12433?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-124317libexpat through 2.10.0 contains an out-of-bounds read vulne…4.8
- CVE-2026-124318Treeio through 2.0 contains an insecure deserialization vuln…7.2
- CVE-2026-12432The WP Full Stripe Free plugin for WordPress is vulnerable t…5.3
- CVE-2026-124326A flaw has been found in DataLinkDC Dinky up to 1.2.5. Impac…5.4
- CVE-2026-124328A vulnerability has been found in FlowCI flow-core-x up to 1…7.4
- CVE-2026-124329A vulnerability was found in FlowCI flow-core-x up to 1.23.4…5
- CVE-2026-124330A vulnerability was determined in FlowCI flow-core-x up to 1…5
- CVE-2026-124331A vulnerability was identified in Jinher OA C6. This impacts…7.3
- CVE-2026-12434The List category posts plugin for WordPress is vulnerable t…4.3
- CVE-2026-12435The Motors – Car Dealership & Classified Listings Plugin plu…4.3
- CVE-2026-12436GitLab has remediated an issue in GitLab CE/EE affecting all…8.4
- CVE-2026-12437Use after free in WebShare in Google Chrome on Windows prior…8.3
Are you affected by CVE-2026-12433?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
