CVE-2025-68027

Hydra Booking <= 1.1.32 - Unauthenticated Privilege Escalation

2026-01-21 00:00
daroo

Strategic Overview

Status
Patched in 1.1.33
Affected Plugin
Hydra Booking — Appointment Scheduling & Booking Calendar
Affected Version
<= 1.1.32
CVSS
9.8Critical
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2025-68027
View all Hydra Booking — Appointment Scheduling & Booking Calendar vulnerabilities

At a glance

CVE-2025-68027 is a critical-severity Improper Privilege Management vulnerability in the Hydra Booking WordPress plugin, affecting versions <= 1.1.32. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.1.33; sites on affected versions should update now. Disclosed January 2026, reported by daroo.

Vulnerability Overview

The Hydra Booking — Appointment Scheduling & Booking Calendar plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.1.32. This makes it possible for unauthenticated attackers to elevate their privileges to that of an administrator.

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

CWE-269: Improper Privilege Management

Reaching this weakness in Hydra Booking <= 1.1.32 takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Hydra Booking the fix is 1.1.33: builds <= 1.1.32 are affected, anything from 1.1.33 onward is not.

Remediation

Update to version 1.1.33, 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.33 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-68027https://www.wordfence.com/threat-intel/vulnerabilities/id/a0998721-7b5e-4657-894c-52dfadde5d4ahttps://nvd.nist.gov/vuln/detail/CVE-2025-68027

Related records

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