Hydra Booking — Appointment Scheduling & Booking Calendar
Approved changes feed: RSS · Atom
cpe:2.3:a:themefic:hydra_booking_—_appointment_scheduling_&_booking_calendar:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Themefic (69fae1e1-81cb-5dd5-92a6-9e186c18d282) |
|---|---|
| Product | Hydra Booking — Appointment Scheduling & Booking Calendar (b97b5c64-5c5b-520c-9d5e-92109f5d1254) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-12433 |
vulnerable | 2026-07-29 00:23:32.331578 |
Hydra Booking <= 1.2.1 - Authenticated (Custom+) Insecure Direct Object Reference to Sensitive Information Exposure via 'booking_id' Parameter
MEDIUM (4.3)
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.
Published: 2026-07-09T08:31:35.571Z
Updated: 2026-07-09T14:37:17.193Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-12788 |
vulnerable | 2026-06-08 07:04:30.974491 |
Hydra Booking – All in One Appointment Booking System | Appointment Scheduling, Booking Calendar & WooCommerce Bookings <= 1.1.27 - Missing Payment Verification to Unauthenticated Payment Bypass
MEDIUM (5.3)
The Hydra Booking — Appointment Scheduling & Booking Calendar plugin for WordPress is vulnerable to missing payment verification to unauthenticated payment bypass in all versions up to, and including, 1.1.27. This is due to the plugin accepting client-controlled payment confirmation data in the tfhb_meeting_paypal_payment_confirmation_callback function without server-side verification with PayPal's API. This makes it possible for unauthenticated attackers to bypass payment requirements and confirm bookings as paid without any actual payment transaction occurring.
Published: 2025-11-11T11:03:46.212Z
Updated: 2026-04-08T17:16:59.618Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-12787 |
vulnerable | 2026-06-08 07:04:30.974120 |
Hydra Booking – All in One Appointment Booking System | Appointment Scheduling, Booking Calendar & WooCommerce Bookings <= 1.1.27 - Unauthenticated Arbitrary Booking Cancellation via Weak Hash Generation
MEDIUM (5.3)
The Hydra Booking — Appointment Scheduling & Booking Calendar plugin for WordPress is vulnerable to unauthorized booking cancellation in all versions up to, and including, 1.1.27. This is due to the plugin's "tfhb_meeting_form_submit_callback" function using insufficiently random values to generate booking cancellation tokens, combined with a globally shared nonce. This makes it possible for unauthenticated attackers to cancel arbitrary bookings via brute force attacks against the tfhb_meeting_form_cencel AJAX endpoint.
Published: 2025-11-11T11:03:45.316Z
Updated: 2026-04-08T16:50:23.131Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.