dbcve.org
Scheduling PluginWordPress extension · Startbooking

CVE-2024-1634

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-18
Fix available
A fix is available. Upgrade to after 3.5.10 or later.
See remediation →
74/100
Remediation priority · Elevated
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 Scheduling Plugin – Online Booking for WordPress plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'cbsb_disconnect_settings' function in all versions up to, and including, 3.5.10. This makes it possible for unauthenticated attackers to disconnect the plugin from the startbooking service and remove connection data.

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 WordPress plugin 'The Scheduling Plugin – Online Booking' has a broken access control vulnerability in the 'cbsb_disconnect_settings' function. This function lacks a capability check, allowing any unauthenticated user to call it. Attackers can exploit this to disconnect the plugin from the startbooking service and erase connection data, causing denial of service to the booking functionality.

MitigationUpdate the plugin to version 3.5.11 or later once available. If no patch exists, consider temporarily disabling the plugin or deploying a WAF rule to block requests to the vulnerable endpoint.

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
Scheduling PluginWordPress extension
Affected:<= 3.5.10

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify if the plugin is installed
    Check your WordPress plugins directory for 'the-scheduling-plugin' or 'startbooking' folder, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if The plugin 'The Scheduling Plugin - Online Booking' or 'Startbooking Scheduling Plugin' appears in your WordPress installation
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and look for the version number of 'The Scheduling Plugin - Online Booking' or 'Startbooking', or inspect the main plugin file (e.g., startbooking.php) for the 'Version' header
    Affected if The version number is 3.5.10 or lower
  3. Verify the vulnerable function exists
    Access your site via FTP or file manager and locate the plugin directory. Search for the function 'cbsb_disconnect_settings' in the plugin PHP files (commonly in includes/ or classes/ folders)
    Affected if The function 'cbsb_disconnect_settings' is found in the plugin code without a capability check (look for 'current_user_can' or 'check_admin_referer' before the function executes)
  4. Check if the plugin is currently connected
    In WordPress admin, navigate to the plugin settings page (usually under Settings > Startbooking or a dedicated Startbooking menu) and check the connection status to startbooking service
    Affected if The plugin shows as connected to the startbooking service (an attacker would need to disconnect an active connection to cause DoS)

Your environment is affected if the Startbooking Scheduling Plugin is installed with version 3.5.10 or lower and the cbsb_disconnect_settings function lacks capability checks, especially if the plugin is actively connected to the startbooking service.

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 3.5.10
Interim mitigation

Update the plugin to version 3.5.11 or later once available. If no patch exists, consider temporarily disabling the plugin or deploying a WAF rule to block requests to the vulnerable endpoint.

Recommended fix Moderate confidence

Version 3.5.11 or newer

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Scheduling Plugin' (also known as 'Booking Package' or similar)
  4. Check the current version is 3.5.10 or below
  5. Click 'Update Now' if an update to version 3.5.11 or higher is available
  6. Alternatively, download the latest version from wordpress.org/plugins and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the version number reflects the update
Caveat Minor plugin point releases typically do not introduce breaking changes; always backup before updating

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

Fix this in Scheduling Plugin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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