dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-6175

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 Ultra Pro Appointments Booking Calendar Plugin plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the multiple functions called via AJAX like save_fields_settings, bup_delete_user_avatar, bup_crop_avatar_user_profile_image, and more in all versions up to, and including, 1.1.13. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify and delete. multiple plugin options and data such as payments, pricing, booking information, business hours, calendars, profile information, and email templates.

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 Ultra Pro WordPress plugin lacks authorization checks on multiple AJAX endpoints (save_fields_settings, bup_delete_user_avatar, bup_crop_avatar_user_profile_image, and others). Any authenticated user with Subscriber-level permissions can invoke these functions to modify or delete plugin settings, payment configurations, pricing, bookings, business hours, calendars, profiles, and email templates.

MitigationUpdate to version 1.1.14 or later which includes proper capability/authorization checks on AJAX functions. Until then, restrict user registration or disable the plugin.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Verify Booking Ultra Pro plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Booking Ultra Pro' or check the plugin files in /wp-content/plugins/bookingultra-pro/ for the main PHP file
    Affected if Plugin is not installed or not present in the plugins directory
  2. Check installed plugin version
    In WordPress admin Plugins list, click 'View Details' on Booking Ultra Pro, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if Version is lower than 1.1.14 (the fixed version)
  3. Identify subscriber-level user accounts
    In WordPress admin, go to Users and look for any accounts with the 'Subscriber' role, or query the wp_users and wp_usermeta tables checking for meta_value 'subscriber'
    Affected if Any Subscriber-level accounts exist in the system
  4. Confirm user registration is enabled
    In WordPress admin, go to Settings > General and check 'Membership: Anyone can register' is checked, or check the 'users_can_register' option in wp_options table
    Affected if Anyone can register is enabled, allowing attackers to create Subscriber accounts

User is affected if Booking Ultra Pro version is below 1.1.14 AND the site has subscriber-level users or allows user registration.

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 1.1.14 or later which includes proper capability/authorization checks on AJAX functions. Until then, restrict user registration or disable the plugin.

Recommended fix Moderate confidence

Upgrade to the latest version available on wordpress.org (version higher than 1.1.13)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Booking Ultra Pro Appointments Booking Calendar Plugin'
  4. Check if an update is available and install the latest version
  5. If no update is shown in WordPress, manually download the latest version from wordpress.org/plugins/booking-ultra-pro and upload via Plugins > Add New > Upload Plugin
  6. Verify the updated version is greater than 1.1.13

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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