VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

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

CVE-2025-12788Published · Updated

Action summary

Affected: ≤1.1.27Update to 1.1.28 or newer

All remediation steps
Watch plugin
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-602 Client-Side Enforcement of Server-Side Security
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

Hydra Booking — Appointment Scheduling & Booking Calendar hydra-booking

  1. Affected≤ 1.1.27
  2. Patched in1.1.28

Update to 1.1.28 or newer.

You are affected if you run ≤ 1.1.27. Version 1.1.28 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Hydra Booking — Appointment Scheduling & Booking Calendar.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 1.1.28, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Hydra Booking — Appointment Scheduling & Booking Calendar to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Ahmad Salem (a7mad.cc).

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Hydra Booking — Appointment Scheduling & Booking Calendar

All 17
More vulnerabilities in Hydra Booking — Appointment Scheduling & Booking Calendar
SeverityVulnerabilityCVEPublished
Medium4.3Authenticated (Hydra Host+) Insecure Direct Object Reference
≤1.2.2Update to 1.2.3
CVE-2026-92421
Medium4.3Authenticated (Hydra Host+) Insecure Direct Object Reference
≤1.2.1Update to 1.2.2
CVE-2026-92420
Medium4.3Authenticated (Hydra Host+) Insecure Direct Object Reference
≤1.2.3Update to 1.2.4
CVE-2026-92425
Medium6.4Authenticated (Host+) Stored Cross-Site Scripting via 'first_name' Parameter
≤1.2.2Update to 1.2.3
CVE-2026-15948
Medium5.3Missing Authorization
≤1.2.2Update to 1.2.3
CVE-2026-28188

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?