BookingpressWordPress extension · Reputeinfosystems
CVE-2024-34799
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 · uneditedMissing Authorization vulnerability in Repute Infosystems BookingPress.This issue affects BookingPress: from n/a through 1.0.82.
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 confidenceMissing Authorization vulnerability in BookingPress plugin allows users to access functionality or perform actions without proper permission checks. The specific affected endpoints or actions are not detailed in the CVE description.
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
< 1.0.83CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate BookingPress plugin installationCheck for the BookingPress plugin directory at /wp-content/plugins/bookingpress-appointment-booking/ or query the WordPress options table for 'active_plugins' to see if bookingpress is listedAffected if The plugin directory exists or bookingpress appears in active plugins list
-
Identify installed BookingPress versionCheck the plugin main file header (e.g., bookingpress-appointment-booking.php) for the 'Version' comment, or query the wp_options table for option_name = 'bookingpress_version'Affected if Version returned is below 1.0.83 (e.g., 1.0.82, 1.0.80, etc.)
-
Verify plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm BookingPress shows as 'Active', or query wp_options for 'active_plugins' containing 'bookingpress'Affected if Plugin is active and version is below 1.0.83
-
Confirm vulnerability scopeSince specific endpoints are not enumerated in the CVE, the vulnerability applies to any booking-related actions (appointments, bookings, customer data) when the plugin is active below version 1.0.83Affected if Plugin is active and version is below 1.0.83, meaning authorization checks are missing on booking functions
You are affected if the BookingPress plugin is installed, active, and running a version lower than 1.0.83, as the missing authorization vulnerability exists in all prior versions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.83
Update BookingPress to version 1.0.83 or later where proper authorization checks have been implemented. If immediate update is not possible, review access control logic around sensitive booking functions.
BookingPress 1.0.83
- Upgrade BookingPress to version 1.0.83 or later to resolve the missing authorization vulnerability
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
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-34799 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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