dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-68055

HIGH · 8.5 CVSS v3.1 Published 2025-12-16
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.32.

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 Themefic Hydra Booking plugin (versions <= 1.1.32) allows attackers to inject malicious SQL commands through unsanitized user input, potentially enabling data exfiltration, modification, or unauthorized administrative access.

MitigationUpdate Hydra Booking plugin to latest version once patched; if no patch available, disable plugin until remediation. Apply web application firewall rules to filter SQL injection patterns as interim protection.

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. Locate Hydra Booking plugin installation
    Search the web root directory for the Themefic Hydra Booking plugin folder, typically found in /wp-content/plugins/ directory under a folder named 'hydra-booking' or similar Themedic naming convention
    Affected if Plugin folder exists on the server
  2. Identify installed plugin version
    Open the main plugin PHP file (usually named hydra-booking.php or similar) and locate the version definition in the plugin header comment, or check the readme.txt file for the Version field
    Affected if Version number is 1.1.32 or lower
  3. Confirm plugin is active
    If using WordPress admin, navigate to Plugins > Installed Plugins and verify Hydra Booking shows as 'Active', or check the wp_options table for active_plugins entry containing 'hydra-booking'
    Affected if Plugin is currently enabled on the WordPress site
  4. Identify vulnerable code pattern (optional)
    Search plugin PHP files for direct SQL queries using $wpdb->prepare, $wpdb->query, or similar without proper input sanitization on user-supplied parameters
    Affected if Unsanitized user input is found in SQL query functions

System is affected if Hydra Booking plugin version 1.1.32 or lower is installed and active on WordPress, exposing the site to SQL injection via unsanitized user input.

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 Hydra Booking plugin to latest version once patched; if no patch available, disable plugin until remediation. Apply web application firewall rules to filter SQL injection patterns as interim protection.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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