CVE-2025-12788

Hydra Booking – All in One Appointment Booking System | Appointment Scheduling, Booking Calendar & WooCommerce Bookings <= 1.1.27 - Missing Payment Verification to Unauthenticated Payment Bypass

2025-11-10 22:39
Ahmad Salem (a7mad.cc)

Strategic Overview

Status
Patched in 1.1.28
Affected Plugin
Hydra Booking — Appointment Scheduling & Booking Calendar
Affected Version
<= 1.1.27
CVSS
5.3Medium
Weakness type
CWE-602 · Client-Side Enforcement of Server-Side Security
CVE
CVE-2025-12788
View all Hydra Booking — Appointment Scheduling & Booking Calendar vulnerabilities

At a glance

CVE-2025-12788 is a medium-severity Client-Side Enforcement of Server-Side Security vulnerability in the Hydra Booking WordPress plugin, affecting versions <= 1.1.27. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.28; sites on affected versions should update now. Disclosed November 2025, reported by Ahmad Salem (a7mad.cc).

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-602: Client-Side Enforcement of Server-Side Security

The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.

Remediation

Update to version 1.1.28, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Hydra Booking 1.1.28 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-12788https://www.wordfence.com/threat-intel/vulnerabilities/id/b49ce4a2-52ad-4824-86fc-5edd2e33802dhttps://nvd.nist.gov/vuln/detail/CVE-2025-12788

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C