CVE-2026-39541
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 · uneditedImproper 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.38.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in Themefic Hydra Booking WordPress plugin allows authenticated attackers to inject malicious JavaScript code through unsanitized input fields. This code is then stored in the database and executed when other users view affected 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
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Hydra Booking plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Hydra Booking' by Themefic, or check the file /wp-content/plugins/ for a hydra-booking directoryAffected if The plugin is present in the installation
-
Identify installed plugin versionCheck the plugin header in /wp-content/plugins/hydra-booking/includes/ or view the version in the WordPress plugin admin listAffected if Any version prior to the patched release is potentially affected; compare against vendor release notes when available
-
Confirm booking forms are accessible to authenticated usersNavigate to the Hydra Booking settings and check which user roles can access and submit booking forms (Users > All Users > select role capabilities, or check Hydra Booking > Settings > GeneralAffected if Any authenticated user (subscriber, customer, or lower privilege) can access and submit to booking form fields
-
Inspect booking form input fields for sanitizationView page source of any public booking form and examine the HTML input fields; check plugin source code in /wp-content/plugins/hydra-booking/includes/ for form handling functions (look for missing sanitize_text_field, esc_attr, or esc_html on user inputs)Affected if Input fields accept raw user input without server-side sanitization functions applied
-
Examine database for suspicious stored scriptsQuery the WordPress database tables where Hydra Booking stores form submissions (typically wp_postmeta or custom tables); look for patterns like <script, javascript:, onload=, onerror= in stored valuesAffected if Database contains HTML or JavaScript patterns in booking submission fields that could execute when viewed
A user is affected if the Hydra Booking plugin is installed and its booking forms accept input from authenticated users without proper input sanitization and output encoding.
Generated from the published advisory. Verify against your own configuration.
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 dataApply output encoding and input sanitization to all user-supplied data before rendering; update Hydra Booking to the latest patched version once released.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39541 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39541 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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