dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2024-10729

HIGH · 8.8 CVSS v3.1 Published 2024-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Booking & Appointment Plugin for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'save_google_calendar_data' function in versions up to, and including, 6.9.0. This makes it possible for authenticated attackers, with subscriber-level permissions or above to update the site options arbitrarily.

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 Booking & Appointment Plugin for WooCommerce plugin has a broken access control vulnerability where the 'save_google_calendar_data' function lacks a capability check, allowing any authenticated user with subscriber-level permissions or higher to arbitrarily modify site options.

MitigationUpdate to version 6.9.1 or later which includes proper capability validation; alternatively, verify that only Administrator-level users can access the affected function.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Booking & Appointment Plugin for WooCommerce' or check the /wp-content/plugins/booking-appointment-ecommerce-directory/ directory exists
    Affected if The plugin is not installed on the WordPress site
  2. Identify the installed version
    In WordPress admin, find the plugin in Plugins > Installed Plugins and read the version number displayed beneath the plugin name; alternatively, check the version in the plugin's main PHP file header or composer.json
    Affected if The version number is lower than 6.9.1 (for example, 6.9.0, 6.8.x, etc.)
  3. Verify Google Calendar integration is in use
    Navigate to the plugin settings (usually under WooCommerce > Booking > Calendar Integration or similar) and check if Google Calendar sync is enabled or configured
    Affected if Google Calendar integration is enabled or has been configured at least once (the vulnerable save_google_calendar_data function handles this feature)
  4. Inspect user role permissions
    Go to WordPress Users > Users and review which roles exist; check if any roles below Administrator (such as Subscriber, Contributor, Author, Editor, or custom roles) are present on the site
    Affected if Any authenticated user with subscriber-level access or higher exists on the site who should not have access to plugin settings

The site is affected if the plugin is installed with a version lower than 6.9.1 AND Google Calendar integration is or was enabled, allowing any logged-in user with subscriber-level permissions to modify site options via the vulnerable function.

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 to version 6.9.1 or later which includes proper capability validation; alternatively, verify that only Administrator-level users can access the affected function.

Recommended fix Moderate confidence

Version 6.9.1 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Booking & Appointment Plugin for WooCommerce' by Tyche Softwares
  4. 4. Check the current installed version number
  5. 5. If the installed version is 6.9.0 or lower, navigate to Plugins > Add New > Upload Plugin
  6. 6. Upload and install the latest version of the plugin (version 6.9.1 or later) from the WordPress repository or from Tychesoftwares.com
  7. 7. Alternatively, update directly from the WordPress admin if an update is available under Plugins > Installed Plugins
  8. 8. After updating, verify the 'save_google_calendar_data' function now includes proper capability checks

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

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-2024-10729 — 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-10729 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