dbcve.org
Woocommerce BookingsWordPress extension · Automattic

CVE-2023-47787

HIGH · 8.8 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to 2.0.4 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-Site Request Forgery (CSRF) vulnerability in WooCommerce WooCommerce Bookings.This issue affects WooCommerce Bookings: from n/a through 2.0.3.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in WooCommerce Bookings plugin allows attackers to induce authenticated users to perform unintended actions. The lack of proper CSRF token validation on state-changing requests enables malicious actors to craft forged requests on behalf of logged-in users.

MitigationUpdate WooCommerce Bookings to the latest version which includes anti-CSRF token implementation. Until then, consider disabling the bookings functionality or implementing additional origin/referer header validation at the web server level as a temporary workaround.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Woocommerce BookingsWordPress extension
Affected:< 2.0.4

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Confirm WooCommerce Bookings plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the wp-content/plugins/ directory for a folder named woocommerce-bookings or similar
    Affected if The WooCommerce Bookings plugin is present in the installation
  2. Check the installed version of WooCommerce Bookings
    In WordPress admin, go to Plugins > Installed Plugins > WooCommerce Bookings and read the version number from the plugin metadata, or open the main plugin file (e.g., woocommerce-bookings.php) and look for the 'Version' header
    Affected if The version number is less than 2.0.4 (e.g., 2.0.3, 2.0.2, 1.x.x)
  3. Identify state-changing request handlers
    Examine the plugin PHP files in wp-content/plugins/woocommerce-bookings/includes/ for form handlers or AJAX endpoints that process POST or GET requests which modify booking data (e.g., creating, updating, or canceling bookings)
    Affected if State-changing request handlers exist in the plugin without proper CSRF token validation
  4. Inspect CSRF token validation in request handlers
    Open the identified state-changing request handler files and search for wp_verify_nonce, wp_create_nonce, or 'nonce' validation logic before processing the request
    Affected if No nonce or CSRF token verification is found in the state-changing request handling code, or the validation is present but incorrectly implemented

A user is affected if WooCommerce Bookings is installed with a version lower than 2.0.4 and the plugin lacks proper CSRF token validation on its state-changing request handlers.

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
Upgrade available Upgrade to 2.0.4 or later
Fixed in 2.0.4
Interim mitigation

Update WooCommerce Bookings to the latest version which includes anti-CSRF token implementation. Until then, consider disabling the bookings functionality or implementing additional origin/referer header validation at the web server level as a temporary workaround.

Recommended fix High confidence

WooCommerce Bookings 2.0.4

  1. 1. Back up your WordPress site and database before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins > Installed Plugins
  4. 4. Locate WooCommerce Bookings in the plugin list
  5. 5. If an update is available, click 'Update Now' to update to version 2.0.4 or later
  6. 6. After updating, verify the plugin version shows 2.0.4 or higher in the plugins list
  7. 7. Test the booking functionality to ensure the update did not break existing features
  8. 8. Consider implementing additional CSRF protections at the server level (e.g., implementing nonces for forms)
Caveat Review WooCommerce Bookings 2.0.4 release notes for any changes that may affect your booking workflows

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

Fix this in Woocommerce Bookings 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 the upgrade done

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-2023-47787 — 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-2023-47787 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