dbcve.org
BookingpressWordPress extension · Reputeinfosystems

CVE-2023-51405

CRITICAL · 9.8 CVSS v3.1 Published 2024-04-24
Fix available
A fix is available. Upgrade to 1.0.75 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
Improper Authentication vulnerability in Repute Infosystems BookingPress allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects BookingPress: from n/a through 1.0.74.

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

Improper authentication in BookingPress plugin allows unauthenticated or improperly authenticated users to access administrative functions that should be constrained by ACLs. This is a critical authentication/authorization bypass vulnerability affecting versions up to 1.0.74, enabling attackers to potentially invoke sensitive functionality without proper credentials.

MitigationUpdate BookingPress to the latest version immediately. If patching is not possible immediately, restrict access to the plugin's admin URLs at the web server level or disable the plugin until a patch can be applied.

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.75

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. Locate BookingPress plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'bookingpress' or 'bookingpress-appointment-booking'. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins to see if BookingPress appears in the list.
    Affected if The plugin folder or entry is not found in the WordPress installation.
  2. Read the installed version number
    If accessing the WordPress file system, open the main plugin file (usually bookingpress/bookingpress.php) and locate the 'Version' header in the plugin comments at the top. In WordPress admin, view the plugin details page to see the version number displayed.
    Affected if The version displayed is less than 1.0.75.
  3. Verify plugin activation status
    In WordPress admin, check if BookingPress shows as 'Active' under the plugin status. Alternatively, check the wp_options table for option_name 'active_plugins' and verify 'bookingpress/bookingpress.php' is included.
    Affected if The plugin is active and version is below 1.0.75.
  4. Confirm the WordPress installation is accessible externally
    Verify the WordPress site is live and the bookingpress plugin files are served over the web. Check if the vulnerable endpoint pattern (wp-admin/admin-ajax.php?action=bookingpress_front) is reachable.
    Affected if The site is live, BookingPress is active, and the version is below 1.0.75, indicating potential exposure to the authentication bypass.

A user is affected if the BookingPress plugin is installed, active, and running version 1.0.74 or lower in a live WordPress environment.

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.75 or later
Fixed in 1.0.75
Interim mitigation

Update BookingPress to the latest version immediately. If patching is not possible immediately, restrict access to the plugin's admin URLs at the web server level or disable the plugin until a patch can be applied.

Recommended fix High confidence

BookingPress version 1.0.75 or later

  1. 1. Create a complete backup of your WordPress site (database and files) before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Locate the BookingPress plugin in the list
  4. 4. Click 'Update now' if an update is available, or manually upload version 1.0.75 or later from the WordPress repository
  5. 5. After updating, verify the plugin version shows 1.0.75 or higher under the Plugins list
  6. 6. Test critical booking workflows (appointment creation, customer registration, payment processing) to ensure functionality works correctly
  7. 7. Review user access controls and ACL configurations to confirm the authentication fix is properly enforced

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

Fix this in Bookingpress Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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