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

CVE-2026-2231

HIGH · 7.2 CVSS v3.1 Published 2026-03-26
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 Fluent Booking plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple parameters in all versions up to, and including, 2.0.01 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.

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 Fluent Booking WordPress plugin up to version 2.0.01 contains a stored XSS vulnerability due to improper input sanitization and output escaping on multiple parameters. Unauthenticated attackers can inject malicious JavaScript that executes when users access affected pages.

MitigationUpdate Fluent Booking plugin to version 2.0.02 or later. If no patched version exists, implement input sanitization using WordPress sanitization functions and output escaping with esc_html()/esc_attr() on all user-supplied 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 Fluent Booking plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Fluent Booking' in the list. Note whether it is installed and active.
    Affected if Plugin is installed and active with a version up to 2.0.01
  2. Check installed plugin version
    Click on the Fluent Booking plugin in the WordPress plugins list to view details, or check the plugin header in wp-content/plugins/fluent-booking/fluent-booking.php for the 'Version' defined constant.
    Affected if Version displayed is 2.0.01 or lower (any version up to and including 2.0.01)
  3. Inspect plugin database for stored scripts
    Access the WordPress database (via phpMyAdmin or WP-CLI) and query the plugin's custom tables (typically prefixed with wp_fluent_booking_ or wp_fb_) for any records containing script tags, javascript:, or onerror/onload attributes in text fields.
    Affected if Any records contain unescaped HTML/script content that could execute when viewed
  4. Identify user-submittable input fields
    Review the plugin's public-facing forms (booking forms, settings pages) and check if user-supplied data in fields such as name, email, phone, or custom fields is stored and displayed without sanitization.
    Affected if Plugin accepts and displays user input without proper sanitization functions (esc_html, esc_attr, sanitize_text_field)
  5. Verify output escaping on frontend pages
    View the source code of pages where booking data is rendered (appointment confirmations, admin dashboards) and check if user-supplied values are wrapped in esc_html() or esc_attr() functions.
    Affected if User-supplied values appear in HTML output without escaping functions

The environment is affected if Fluent Booking plugin version 2.0.01 or lower is active and the plugin stores or displays user input without sanitization and escaping.

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 Fluent Booking plugin to version 2.0.02 or later. If no patched version exists, implement input sanitization using WordPress sanitization functions and output escaping with esc_html()/esc_attr() on all user-supplied parameters before rendering.

Recommended fix Moderate confidence

Latest version of Fluent Booking plugin (above 2.0.01)

  1. Check your current Fluent Booking plugin version in WordPress admin under Plugins > Installed Plugins
  2. If your version is 2.0.01 or below, navigate to Dashboard > Updates or go to Plugins > Add New > Upload Plugin
  3. Download the latest version of Fluent Booking from the official WordPress repository or from the developer's site
  4. Upload and install the updated plugin, then activate it
  5. Verify the fix by confirming the plugin version is above 2.0.01
Caveat Review plugin settings and calendar configurations after upgrade as behavior may have changed

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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