dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-49377

MEDIUM · 6.3 CVSS v3.1 Published 2025-10-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in Themefic Hydra Booking hydra-booking allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Hydra Booking: from n/a through <= 1.1.9.

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 · moderate confidence

Missing authorization vulnerability in the Themefic Hydra Booking WordPress plugin (versions <= 1.1.9) allows authenticated attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to booking management functions or data that should require higher privilege levels.

MitigationUpdate to the latest version of Hydra Booking when available; review and enforce proper capability checks and nonce verification on all administrative functions.

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
Low
Integrity
Low
Availability
Low

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

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. Confirm Hydra Booking plugin installation
    In WordPress admin, navigate to Plugins > Installed Plugins and locate 'Hydra Booking' or check the plugin files in wp-content/plugins/hydra-booking/ for the main plugin file header
    Affected if The plugin is not found in the WordPress installation
  2. Identify installed plugin version
    Open the main plugin file (usually hydra-booking.php) and locate the 'Version' header in the plugin comment block, or check the WordPress plugins admin page for the version number
    Affected if Version is 1.1.9 or lower
  3. Verify WordPress user role configuration
    Navigate to WordPress Users panel and review what roles have access to Hydra Booking-related capabilities or admin pages
    Affected if Lower-privileged roles (such as Subscriber or Contributor) have access to booking management functions
  4. Inspect plugin capability settings
    If the plugin has a settings page (usually under Settings > Hydra Booking or under the plugin menu), check the access control or capability configuration options for any misconfigured permission levels
    Affected if The plugin allows authenticated users with low-level permissions to access administrative booking functions

A user is affected if Hydra Booking plugin version 1.1.9 or lower is installed and low-privileged authenticated users can access booking management functions that should require higher privileges.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Hydra Booking when available; review and enforce proper capability checks and nonce verification on all administrative functions.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49377 — 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-49377 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