dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-6960

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 BookingPress Pro plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'bookingpress_validate_submitted_booking_form_func' function in all versions up to, and including, 5.6. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. Note: The vulnerability can only be exploited if a signature custom field is added to the booking form.

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 BookingPress Pro WordPress plugin lacks proper file type validation in the bookingpress_validate_submitted_booking_form_func function, allowing unauthenticated attackers to upload arbitrary files to the server. Successful exploitation enables remote code execution, though the attack surface requires a signature custom field to exist on the booking form.

MitigationUpdate BookingPress Pro to the latest version when available, or remove signature custom fields from booking forms if not essential; consider WAF rules to block suspicious file upload requests as an interim measure.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify BookingPress Pro is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'bookingpress' or similar Pro variant.
    Affected if BookingPress Pro plugin is found in the WordPress installation
  2. Check installed BookingPress version
    In WordPress admin, go to Plugins > Installed Plugins and find the BookingPress entry to view its version number, or read the main plugin PHP file (e.g., bookingpress.php) and look for the 'Version' header comment.
    Affected if Version number is lower than 5.7 (e.g., 5.6.x, 5.5.x, etc.)
  3. Inspect booking form custom fields for signatures
    In WordPress admin, navigate to BookingPress > Settings > Custom Fields (or similar menu where custom field configuration is stored). Examine the custom fields list for any field of type 'Signature' or fields with signature functionality enabled.
    Affected if At least one signature custom field is configured and active in a booking form
  4. Confirm vulnerability applicability
    Combine the results: the vulnerability requires BOTH an affected version (below 5.7) AND the presence of signature custom fields. Check if both conditions are true simultaneously.
    Affected if BookingPress Pro version is below 5.7 AND one or more signature custom fields exist in the booking form configuration

A user is affected if their WordPress site has BookingPress Pro installed with a version lower than 5.7 and has signature custom fields enabled in any booking form configuration.

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 BookingPress Pro to the latest version when available, or remove signature custom fields from booking forms if not essential; consider WAF rules to block suspicious file upload requests as an interim measure.

Recommended fix Moderate confidence

BookingPress Pro version 5.7 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the BookingPress Pro plugin
  4. 4. Check the current installed version to confirm it is 5.6 or below
  5. 5. Create a complete backup of the WordPress site (database and files)
  6. 6. Navigate to Dashboard > Updates or Plugins page
  7. 7. Update the BookingPress Pro plugin to the latest available version
  8. 8. After updating, verify that the signature custom field configuration is still needed for the exploit

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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