dbcve.org
BookingpressWordPress extension · Reputeinfosystems

CVE-2024-31296

MEDIUM · 5.4 CVSS v3.1 Published 2024-04-07
Fix available
A fix is available. Upgrade to 1.0.82 or later.
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
Authorization Bypass Through User-Controlled Key vulnerability in Repute Infosystems BookingPress.This issue affects BookingPress: from n/a through 1.0.81.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in the BookingPress WordPress plugin that allows attackers to bypass authorization checks by manipulating user-controlled keys. The vulnerability exists in versions up to 1.0.81 and could allow unauthorized access to booking data or administrative functions.

MitigationUpdate BookingPress to the latest version immediately. Review and enforce proper authorization checks on all sensitive endpoints and verify that object references cannot be manipulated by unprivileged users.

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
BookingpressWordPress extension
Affected:< 1.0.82

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 BookingPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'BookingPress - Online Appointment Booking | Scheduling | Reservation Plugin' in the list. Alternatively, check the /wp-content/plugins/bookingpress-appointment-booking/ directory exists on the server.
    Affected if The BookingPress plugin is present in the WordPress installation
  2. Check installed BookingPress version
    Navigate to Plugins > Installed Plugins in WordPress admin, find BookingPress, and note the version number displayed under the plugin name. Or inspect the main plugin file header in /wp-content/plugins/bookingpress-appointment-booking/bookingpress.php for the 'Version' field.
    Affected if The version number is below 1.0.82 (for example: 1.0.81, 1.0.80, etc.)
  3. Identify if booking endpoints are accessible
    Check if any booking-related WordPress REST API endpoints or frontend booking forms are publicly accessible. Look for URLs containing /bookingpress/ or similar patterns in the site's public-facing pages.
    Affected if BookingPress booking functionality is enabled and accessible to unprivileged or unauthenticated users
  4. Review user role permissions for booking data
    Navigate to BookingPress > Settings > General in the WordPress admin. Check which user roles have access to view, edit, or delete bookings. Verify if low-privileged users (such as subscribers or guests) can access booking records.
    Affected if Users with limited privileges (subscriber, customer, or unauthenticated users) can access or modify booking data that should require higher permissions

A WordPress site is affected if BookingPress plugin version is below 1.0.82 and booking endpoints or data are accessible to users who should not have such access according to the principle of least privilege.

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

Update BookingPress to the latest version immediately. Review and enforce proper authorization checks on all sensitive endpoints and verify that object references cannot be manipulated by unprivileged users.

Recommended fix High confidence

1.0.82

  1. Backup your WordPress site before updating
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. Locate BookingPress in the plugin list
  4. Verify current version is below 1.0.82
  5. Update BookingPress to version 1.0.82 or later via the WordPress plugin update mechanism
  6. Alternatively, download BookingPress 1.0.82 from the official WordPress plugin repository and upload manually if automatic update is unavailable

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

Fix this in Bookingpress 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 the upgrade done

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-31296 — 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-31296 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