dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-13746

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Booking Calendar and Notification plugin for WordPress is vulnerable to unauthorized access, modification, and loss of data due to missing capability checks on the wpcb_all_bookings(), wpcb_update_booking_post(), and wpcb_delete_posts() functions in all versions up to, and including, 4.0.3. This makes it possible for unauthenticated attackers to extract data, create or update bookings, or delete arbitrary posts.

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 Calendar and Notification plugin for WordPress versions up to 4.0.3 lacks capability checks on three functions (wpcb_all_bookings, wpcb_update_booking_post, wpcb_delete_posts), allowing unauthenticated attackers to extract booking data, create/modify bookings, and delete arbitrary posts via direct function calls.

MitigationUpgrade to version 4.0.4 or later which implements proper capability checks using current_user_can() on the affected functions. Until patched, consider disabling the plugin or blocking unauthenticated access to WordPress admin areas.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Locate the Booking Calendar plugin files
    Access your WordPress site via FTP or file manager, navigate to /wp-content/plugins/ and look for a folder named 'booking-calendar-notification', 'booking-calendar', or similar naming convention containing 'booking' and 'calendar' in the plugins directory.
    Affected if The plugin folder exists in the plugins directory.
  2. Read the installed plugin version
    Open the main plugin file (usually plugin-name.php) in the plugin folder and locate the version in the plugin header comment (comment block at the top with 'Version: x.x.x').
    Affected if The version listed is 4.0.3 or earlier.
  3. Verify the plugin is active
    Log into WordPress admin, go to Plugins > Installed Plugins, and check if the Booking Calendar plugin is currently activated.
    Affected if The plugin shows as 'Active' and the version is 4.0.3 or earlier.
  4. Confirm WordPress admin access for unauthenticated users
    Try accessing your WordPress admin login page (wp-admin or wp-login.php) from a private/incognito browser window without being logged in. Check if the site allows access or immediately redirects to a login form.
    Affected if The site permits unauthenticated access to admin functionality or the login page is directly accessible (standard for most sites, but indicates the attack surface exists).

If the Booking Calendar and Notification plugin is installed, active, and running version 4.0.3 or earlier, the environment is affected by this CVE.

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

Upgrade to version 4.0.4 or later which implements proper capability checks using current_user_can() on the affected functions. Until patched, consider disabling the plugin or blocking unauthenticated access to WordPress admin areas.

Recommended fix High confidence

Booking Calendar and Notification version 4.0.4 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Booking Calendar and Notification' plugin
  4. Check if the current version is 4.0.3 or earlier
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin version is 4.0.4 or higher

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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