dbcve.org
BookingpressWordPress extension · Reputeinfosystems

CVE-2023-36507

MEDIUM · 5.3 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to after 1.0.64 or later.
See remediation →
62/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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Repute Infosystems BookingPress – Appointment Booking Calendar Plugin and Online Scheduling Plugin.This issue affects BookingPress – Appointment Booking Calendar Plugin and Online Scheduling Plugin: from n/a through 1.0.64.

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 BookingPress WordPress plugin versions up to 1.0.64 contains an information disclosure vulnerability allowing unauthenticated actors to access sensitive information. The specific nature of the exposed data is not detailed in available documentation, but CVSS metrics indicate network-based exploitation with no privileges required and low confidentiality impact.

MitigationUpdate BookingPress plugin to version 1.0.65 or later where the vulnerability is patched. Review access logs for any signs of exploitation during the vulnerable period.

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

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 search for BookingPress. Alternatively, check the /wp-content/plugins/bookingpress-appointment-booking directory exists on the server.
    Affected if The BookingPress plugin directory exists and the plugin is active in WordPress.
  2. Check installed BookingPress version
    In WordPress admin, go to Plugins > Installed Plugins and locate BookingPress. The version number is displayed below the plugin name. Alternatively, check the main plugin PHP file for the Version header comment.
    Affected if The installed version is 1.0.64 or lower.
  3. Confirm WordPress site exposes BookingPress to unauthenticated users
    Attempt to access common BookingPress endpoints (such as wp-json/bookingpress/v1/ or ajax handlers) without logging in. Use a browser or curl command: curl -I https://yoursite.com/wp-json/bookingpress/v1/
    Affected if The endpoints return data without requiring authentication (HTTP 200 responses without login cookies).
  4. Review access logs for BookingPress-related requests
    Examine web server access logs (Apache access_log, Nginx access.log) for unusual or批量 requests to bookingpress-related URLs, especially from unauthenticated IP addresses. Look for patterns like repeated GET requests to bookingpress endpoints.
    Affected if Log entries show excessive or anomalous requests to BookingPress endpoints from unauthenticated sources.

If BookingPress plugin version 1.0.64 or lower is installed and active, and its endpoints are accessible without authentication, the environment is likely affected by this vulnerability.

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.

From vendor data
Upgrade available Upgrade to a release after 1.0.64
Interim mitigation

Update BookingPress plugin to version 1.0.65 or later where the vulnerability is patched. Review access logs for any signs of exploitation during the vulnerable period.

Fix this in Bookingpress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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