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

CVE-2026-40791

HIGH · 7.1 CVSS v3.1 Published 2026-06-15
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

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
Unauthenticated Cross Site Scripting (XSS) in WP Time Slots Booking Form <= 1.2.46 versions.

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

Unauthenticated Cross Site Scripting (XSS) vulnerability in WP Time Slots Booking Form plugin for WordPress versions 1.2.46 and below allows remote attackers to inject malicious JavaScript code without requiring any authentication.

MitigationUpdate the WP Time Slots Booking Form plugin to a version newer than 1.2.46, or disable/remove the plugin until a patched version is available.

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 plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WP Time Slots Booking Form' in the list, or check the /wp-content/plugins/ directory for the plugin folder
    Affected if Plugin folder 'wp-time-slots-booking-form' exists in the plugins directory
  2. Identify installed version
    In the plugins list, find the WP Time Slots Booking Form entry and read the version number displayed beneath the plugin name. Alternatively, open /wp-content/plugins/wp-time-slots-booking-form/readme.txt and check the version in the header section
    Affected if Version number is 1.2.46 or lower
  3. Verify plugin is active
    In WordPress admin > Plugins, confirm the plugin status shows as 'Active'. Also check if any shortcode or widget from this plugin is in use on live pages
    Affected if Plugin is active and exposed on any public-facing page via shortcode, widget, or block
  4. Confirm vulnerability scope
    Since this is an unauthenticated XSS, any page loading the plugin's frontend functionality is potentially vulnerable. Check pages using [wp_time_slots_booking_form] shortcode or equivalent
    Affected if Plugin version is <= 1.2.46 AND plugin outputs to frontend without sanitization

You are affected if the WP Time Slots Booking Form plugin is installed at version 1.2.46 or below and the plugin is active or its shortcode is used on any accessible 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WP Time Slots Booking Form plugin to a version newer than 1.2.46, or disable/remove the plugin until a patched version is available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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