dbcve.org
Woocommerce BookingsWordPress extension · Automattic

CVE-2023-32747

HIGH · 7.5 CVSS v3.1 Published 2023-12-21
Fix available
A fix is available. Upgrade to after 1.15.78 or later.
See remediation →
84/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
Authorization Bypass Through User-Controlled Key vulnerability in WooCommerce WooCommerce Bookings.This issue affects WooCommerce Bookings: from n/a through 1.15.78.

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

Authorization bypass vulnerability in WooCommerce Bookings plugin where an attacker can manipulate a user-controlled key parameter to gain unauthorized access to booking data or functionality. This is an IDOR (Insecure Direct Object Reference) class vulnerability allowing attackers to access or modify bookings they should not have permission to view or edit.

MitigationUpdate WooCommerce Bookings to version 1.15.79 or later. If no patched version exists, contact WooCommerce support or consider disabling the plugin until a fix is available.

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:<= 1.15.78

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Check WooCommerce Bookings plugin version
    Navigate to Plugins > Installed Plugins in WordPress admin. Find 'WooCommerce Bookings' and look at the version number displayed below the plugin name. Alternatively, check the plugin header in /wp-content/plugins/woocommerce-bookings/includes/class-wc-bookings-plugin.php or the main plugin file for the 'Version' header.
    Affected if The installed version is 1.15.78 or lower (any version from the plugin's initial release up to and including 1.15.78).
  2. Confirm the WooCommerce Bookings plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that WooCommerce Bookings is activated. Check for the presence of Booking post types or the booking menu item in the admin sidebar.
    Affected if The plugin is active and running. An inactive plugin would not be exploitable.
  3. Identify if booking functionality is publicly accessible
    Check if the WordPress site has booking capabilities enabled for unauthenticated or low-privileged users. Look for booking forms on the frontend, check the WooCommerce Bookings settings at WooCommerce > Settings > Bookings, and verify if booking creation/modification endpoints are accessible without authentication.
    Affected if Booking creation or modification endpoints are accessible to users without proper authorization checks (guest users, customers, or users without booking admin privileges).

A user is affected if WooCommerce Bookings version 1.15.78 or lower is installed, the plugin is active, and booking endpoints are accessible to unauthenticated or unauthorized users.

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 a release after 1.15.78
Interim mitigation

Update WooCommerce Bookings to version 1.15.79 or later. If no patched version exists, contact WooCommerce support or consider disabling the plugin until a fix is available.

Recommended fix Moderate confidence

Latest version of WooCommerce Bookings (newer than 1.15.78)

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins > WooCommerce Bookings
  3. 3. Check current installed version to confirm it is <= 1.15.78
  4. 4. Update WooCommerce Bookings to the latest available version from the WordPress plugin repository
  5. 5. Verify the update completed successfully
  6. 6. Test booking functionality to ensure the plugin works correctly after update
  7. 7. Confirm that users can only access their own booking data (authorization properly enforced)
Caveat Review plugin changelog for any breaking changes between your current version and the new version

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

Fix this in Woocommerce Bookings Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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