dbcve.org
Booking CalendarWordPress extension · Wpdevart

CVE-2023-24373

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-03
Fix available
A fix is available. Upgrade to 3.2.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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
External Control of Assumed-Immutable Web Parameter vulnerability in WpDevArt Booking calendar, Appointment Booking System allows Manipulating Hidden Fields.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

The WpDevArt Booking Calendar plugin for WordPress contains a parameter tampering vulnerability where hidden form fields can be manipulated by attackers. This allows attackers to modify assumed-immutable values such as pricing, booking availability, or other sensitive parameters directly through the web interface, bypassing intended business logic constraints.

MitigationImplement server-side validation for all parameters, including hidden fields. Replace trust in client-side hidden fields with server-side state management, session-bound tokens, or database-validated values for critical operations.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check if WpDevArt Booking Calendar plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WpDevArt Booking Calendar' in the installed plugins list, or inspect the filesystem at wp-content/plugins/ for a folder named 'booking-calendar'
    Affected if The plugin appears in the installed plugins list or filesystem
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > WpDevArt Booking Calendar and read the version number from the plugin description, or open the main plugin PHP file and look for the 'Version' header comment in the plugin metadata
    Affected if The version number is lower than 3.2.4
  3. Inspect booking form hidden fields
    Create or view a booking form on the frontend of the site, then view the page source (right-click > View Page Source) and search for input elements with type="hidden" within the form
    Affected if Hidden input fields exist that contain sensitive values such as price, availability, or booking constraints without visible counterparts or server-side verification
  4. Test parameter manipulability
    Use browser developer tools to modify a hidden field value (such as a price field) and submit the form, then observe if the modified value is accepted by the server without validation errors
    Affected if The modified hidden field value is accepted and reflected in the booking without server-side rejection

A user is affected if the WpDevArt Booking Calendar plugin is installed with a version lower than 3.2.4 and the booking forms contain manipulable hidden fields handling sensitive parameters.

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 server-side validation for all parameters, including hidden fields. Replace trust in client-side hidden fields with server-side state management, session-bound tokens, or database-validated values for critical operations.

Recommended fix High confidence

Booking Calendar version 3.2.4

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Booking Calendar' (WpDevArt) plugin
  4. Check if the current version is below 3.2.4
  5. If vulnerable, click 'Update Now' to upgrade to version 3.2.4
  6. Alternatively, navigate to Dashboard > Updates and update all plugins
  7. After update, verify the plugin version shows 3.2.4 or higher

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
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,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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