dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-57388

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

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 Input During Web Page Generation ('Cross-site Scripting') vulnerability in Themefic Hydra Booking hydra-booking allows Stored XSS.This issue affects Hydra Booking: from n/a through <= 1.1.44.

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

Stored XSS vulnerability in Themefic Hydra Booking plugin allows attackers to inject malicious JavaScript code through unsanitized input fields. The injected payload is stored in the database and executes when other users view affected pages, potentially compromising admin sessions or defacing content.

MitigationUpdate Hydra Booking to the latest version when available, or apply input sanitization (wp_kses, esc_html, esc_attr) and output encoding to all user-supplied data before rendering in web pages.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 is installed
    Navigate to WordPress admin > Plugins, or inspect /wp-content/plugins/ directory for a folder containing 'hydra-booking' or 'themefic-hydra'
    Affected if The plugin is not present in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin > Plugins > Hydra Booking, view the plugin details to see the version number. Compare against any known fixed version releases.
    Affected if Running an older version of the plugin that has not addressed stored XSS vulnerabilities
  3. Locate booking form input fields
    Access the frontend booking form created by Hydra Booking. Inspect the HTML form elements (input, textarea, select) that accept user data such as name, email, phone, and custom fields.
    Affected if User input fields exist in booking forms that could accept malicious scripts
  4. Inspect database for unsanitized stored data
    Query the WordPress database tables where Hydra Booking stores submissions (typically wp_postmeta or a custom table). Look for HTML tags, script tags, or event handlers in stored field values.
    Affected if Database contains raw HTML or JavaScript in booking submission fields that was not sanitized on input
  5. Verify output rendering lacks sanitization
    View a booking entry in the admin panel or frontend. View page source and check if displayed field values use functions like esc_html, esc_attr, or wp_kses before rendering.
    Affected if User-supplied booking data is rendered in HTML without escaping, allowing injected scripts to execute in browser sessions

You are affected if Hydra Booking plugin is installed, contains unsanitized booking form fields, and stores/displays user input without proper HTML escaping or sanitization functions.

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

Update Hydra Booking to the latest version when available, or apply input sanitization (wp_kses, esc_html, esc_attr) and output encoding to all user-supplied data before rendering in web pages.

Recommended fix Moderate confidence

Latest version of Themefic Hydra Booking (above 1.1.44)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Themefic Hydra Booking plugin
  4. Check if an update is available for Hydra Booking
  5. If an update is available, update to the latest version (above 1.1.44)

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

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-2026-57388 — 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-2026-57388 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