CVE-2025-7689

Hydra Booking 1.1.0 - 1.1.18 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation via tfhb_reset_password_callback Function

2025-07-28 20:38
kr0d

Strategic Overview

Status
Patched in 1.1.19
Affected Version
1.1.0 – 1.1.18
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-7689
View all Hydra Booking — Appointment Scheduling & Booking Calendar vulnerabilities

At a glance

CVE-2025-7689 is a high-severity Missing Authorization vulnerability in the Hydra Booking WordPress plugin, affecting versions 1.1.0 – 1.1.18. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.1.19; sites on affected versions should update now. Disclosed July 2025, reported by kr0d.

Vulnerability Overview

The Hydra Booking plugin for WordPress is vulnerable to Privilege Escalation due to a missing capability check on the tfhb_reset_password_callback() function in versions 1.1.0 to 1.1.18. This makes it possible for authenticated attackers, with Subscriber-level access and above, to reset the password of an Administrator user, achieving full privilege escalation.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

Hydra Booking 1.1.0 – 1.1.18 carries this weakness at tfhb_reset_password_callback(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Hydra Booking the fix is 1.1.19: builds 1.1.0 – 1.1.18 are affected, anything from 1.1.19 onward is not.

Remediation

Update to version 1.1.19, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Hydra Booking 1.1.19 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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