dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-7689

HIGH · 8.8 CVSS v3.1 Published 2025-07-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Hydra Booking WordPress plugin (versions 1.1.0-1.1.18) lacks a capability check on the tfhb_reset_password_callback() function, allowing any authenticated user with Subscriber-level access or higher to reset arbitrary user passwords, including Administrator accounts, resulting in full privilege escalation.

MitigationApply the latest security update for Hydra Booking plugin which adds proper authorization checks to the password reset function. Until then, restrict user registration or monitor for suspicious password reset requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Hydra Booking plugin installation and version
    Navigate to WordPress admin > Plugins and locate 'Hydra Booking' in the installed plugins list. Note the version number displayed. Alternatively, check the plugin header in /wp-content/plugins/hydra-booking/ directory for the Version field.
    Affected if The installed version is 1.1.0 through 1.1.18 (inclusive)
  2. Confirm tfhb_reset_password_callback function exists
    Search the plugin files (particularly in includes/ or functions/ subdirectories) for the function named 'tfhb_reset_password_callback'. Inspect the function code to verify it performs password reset operations.
    Affected if The function exists and contains password reset logic without a current_user_can() or capability check at the function entry point
  3. Identify low-privilege authenticated users
    In WordPress admin > Users, review the user list. Check for any accounts assigned the Subscriber role. Also verify if WordPress user registration is enabled under Settings > General > Membership (checked 'Anyone can register' option).
    Affected if There exists at least one user with Subscriber role OR any user can register new accounts, providing an attacker the means to obtain the minimum required access level
  4. Check for unauthorized password reset activity
    Review WordPress user session logs or security plugins (if installed) for password reset requests initiated by lower-privileged users targeting Administrator accounts. Check server access logs for POST requests to /wp-admin/admin-ajax.php with action 'tfhb_reset_password' or similar.
    Affected if Password reset requests originating from Subscriber-level accounts targeting Administrator or other high-privilege users are present in logs

You are affected if Hydra Booking plugin versions 1.1.0-1.1.18 are installed and the password reset function lacks capability verification, combined with the presence of Subscriber-level users or enabled user registration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest security update for Hydra Booking plugin which adds proper authorization checks to the password reset function. Until then, restrict user registration or monitor for suspicious password reset requests.

Recommended fix Moderate confidence

Latest available version of Hydra Booking plugin (version higher than 1.1.18)

  1. 1. Log in to the WordPress admin dashboard with Administrator privileges.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the Hydra Booking plugin in the list.
  4. 4. Check the current version number of the plugin (displayed under the plugin name).
  5. 5. If an update is available, click 'Update Now' to install the latest version.
  6. 6. After updating, verify the new version number matches a release that includes the security fix.
  7. 7. Test that password reset functionality works correctly for appropriate user roles.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7689 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7689 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data