dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-49378

HIGH · 8.5 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 →
91/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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Themefic Hydra Booking hydra-booking allows SQL Injection.This issue affects Hydra Booking: from n/a through <= 1.1.10.

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

SQL injection vulnerability in the Themefic Hydra Booking WordPress plugin allows unauthenticated attackers to inject malicious SQL commands through unsanitized user input in the plugin's database queries, potentially leading to data exfiltration or administrative access.

MitigationUpgrade to the latest version of Hydra Booking when available; until then, restrict access to the affected endpoints via web server configuration or implement input validation/waf rules as a temporary mitigation.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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. Verify Hydra Booking plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Hydra Booking' by Themefic. Note the installed version number displayed there.
    Affected if The plugin is present and active in the WordPress installation
  2. Check plugin version against known fixed version
    Compare your installed version to the latest version available in the WordPress plugin repository or from Themefic's release notes. If your version is older than the latest, it may be vulnerable.
    Affected if Your installed version predates the patched version (the vendor has not specified the exact version range, so any version older than current is potentially affected)
  3. Inspect plugin database query code for unsanitized input
    Examine the main plugin PHP files (typically in wp-content/plugins/hydra-booking/) for direct use of $_GET, $_POST, or $_REQUEST in SQL queries without $wpdb->prepare() or similar sanitization. Search for patterns like 'SELECT * FROM' concatenated with user input.
    Affected if User-supplied parameters are used directly in SQL queries without prepared statements or escaping functions
  4. Identify accessible endpoints processing user input
    Review the plugin's public-facing PHP files (especially ajax handlers and form processors) that process requests from unauthenticated users. Check for files that handle booking, search, or frontend submission functionality.
    Affected if The plugin exposes endpoints that accept unauthenticated user input and pass it to database queries
  5. Review server and access logs for SQL injection attempts
    Search web server logs (Apache/nginx error and access logs) for suspicious patterns targeting the Hydra Booking plugin URLs, such as SQL keywords (UNION, SELECT, INSERT) in query parameters, especially on paths containing 'hydra-booking' or 'hydra'.
    Affected if Logs show SQL injection payloads being submitted to Hydra Booking endpoints, indicating active exploitation attempts

Your environment is affected if Hydra Booking plugin is installed, your version is older than the patched release, and the plugin processes unauthenticated user input into SQL queries without sanitization.

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

Upgrade to the latest version of Hydra Booking when available; until then, restrict access to the affected endpoints via web server configuration or implement input validation/waf rules as a temporary mitigation.

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-49378 — 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-49378 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