dbcve.org
Booking CalendarWordPress extension · Wpdevart

CVE-2023-24407

HIGH · 8.8 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 3.2.4 or later.
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
Missing Authorization vulnerability in WpDevArt Booking calendar, Appointment Booking System allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Booking calendar, Appointment Booking System: from n/a through 3.2.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

Missing authorization vulnerability in WpDevArt Booking Calendar plugin allows authenticated users to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to booking management functions or data that should require higher privileges.

MitigationImplement proper capability checks and authorization controls on all sensitive endpoints; update to the latest version if available and review user role permissions.

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
Booking CalendarWordPress extension
Affected:< 3.2.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
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. Verify WpDevArt Booking Calendar is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WpDevArt Booking Calendar' in the list of active plugins.
    Affected if The plugin is present and active in the WordPress installation.
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins. Click on the WpDevArt Booking Calendar plugin to view its details, or inspect the main plugin file (typically wpdevart-booking-calendar/includes/booking_admin.php or similar) to find the version comment in the plugin header.
    Affected if The displayed version number is lower than 3.2.4.
  3. Verify WordPress user roles exist
    In WordPress admin, navigate to Users > All Users to see what user roles are configured. Note if any users with Subscriber, Contributor, or Author roles exist.
    Affected if Any authenticated user accounts (Subscriber level or higher) exist in the system.
  4. Test booking management access for low-privileged users
    Log in as a user with Subscriber or Author role. Attempt to access the WpDevArt booking calendar admin pages directly via /wp-admin/admin.php?page=wpdevart-booking-calendar or similar booking management URLs. Observe if booking data or management functions are accessible without being redirected or denied.
    Affected if Lower-privileged users can view or modify booking records or access admin-level booking functions they should not have access to.

A user is affected if WpDevArt Booking Calendar version lower than 3.2.4 is installed and any authenticated WordPress users with limited privileges can access booking management functions that should require administrative capabilities.

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 3.2.4 or later
Fixed in 3.2.4
Interim mitigation

Implement proper capability checks and authorization controls on all sensitive endpoints; update to the latest version if available and review user role permissions.

Recommended fix High confidence

3.2.4

  1. 1. Back up your WordPress site and database before proceeding with any updates.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Find the 'Booking Calendar, Appointment Booking System' (WpDevArt Booking Calendar) plugin.
  5. 5. If an update is available, click 'Update Now' to update to the latest version.
  6. 6. Alternatively, you can download version 3.2.4 from the official WordPress plugin repository and manually upload it via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin version is 3.2.4 or higher.
  8. 8. Test the booking functionality to ensure the update did not break any existing features.

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

Fix this in Booking Calendar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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