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

CVE-2026-8143

HIGH · 7.2 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 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
The HBook plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'hb_country_iso', 'hb_usa_state_iso', and 'hb_canada_province_iso' parameters in all versions up to, and including, 2.1.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page (the HBook Customers admin page).

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

The HBook WordPress plugin versions up to 2.1.6 contain a stored XSS vulnerability in three parameters (hb_country_iso, hb_usa_state_iso, hb_canada_province_iso) used on the HBook Customers admin page. Unauthenticated attackers can inject arbitrary JavaScript via these parameters due to insufficient input sanitization and lack of output escaping, causing the malicious script to execute whenever an admin accesses the affected page.

MitigationUpdate HBook plugin to version 2.1.7 or later; if no update exists, implement proper input sanitization using sanitize_text_field() and output escaping using esc_html() or esc_attr() on the affected parameters before rendering.

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

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

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 HBook plugin is installed
    Go to WordPress admin dashboard > Plugins and look for 'HBook' in the installed plugins list. Note the installed version number displayed below the plugin name.
    Affected if HBook plugin is installed and the version displayed is 2.1.6 or lower
  2. Check database for suspicious parameter values
    Access your WordPress database via phpMyAdmin or command line. Query the options table for records containing 'hb_country_iso', 'hb_usa_state_iso', or 'hb_canada_province_iso'. Examine the stored values for any unexpected characters, script tags, or encoded content.
    Affected if Any of these three parameters contain values with <script> tags, javascript: URIs, or other XSS payloads
  3. Inspect the Customers admin page source
    Navigate to HBook > Customers in the WordPress admin. Right-click and view page source. Search for the strings 'hb_country_iso', 'hb_usa_state_iso', or 'hb_canada_province_iso' and examine the HTML output around these fields.
    Affected if The parameter values appear unescaped in the HTML (visible script tags, unencoded quotes, or event handler attributes)
  4. Verify if public-facing forms accept unsanitized input
    Submit a test booking request using the HBook booking form. In the submission, include a test payload such as 'test"<script>alert(1)</script>' in country/state fields. Then check the Customers admin page to see if this payload renders unescaped.
    Affected if The test payload renders as raw HTML/script instead of being escaped when viewed in the admin panel

You are affected if the HBook plugin version is 2.1.6 or lower AND suspicious values are found in the hb_country_iso, hb_usa_state_iso, or hb_canada_province_iso database entries, or these values render unescaped on the Customers admin page.

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 HBook plugin to version 2.1.7 or later; if no update exists, implement proper input sanitization using sanitize_text_field() and output escaping using esc_html() or esc_attr() on the affected parameters before rendering.

Recommended fix Moderate confidence

Latest version of HBook (after 2.1.6)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find the HBook plugin
  4. 4. If an update is available, click 'Update Now'
  5. 5. Alternatively, download the latest version of HBook from the official WordPress plugin repository or CodeCanyon
  6. 6. Deactivate the current HBook plugin
  7. 7. Upload and install the updated version
  8. 8. Reactivate the plugin

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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