dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-12558

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
The WP BASE Booking of Appointments, Services and Events plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the export_db function in all versions up to, and including, 4.9.2. This makes it possible for authenticated attackers, with Subscriber-level access and above, to expose sensitive information from the database, such as the hashed administrator password.

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 · high confidence

The WP BASE Booking plugin for WordPress has a broken access control vulnerability in the export_db function. The function lacks a capability check, allowing any authenticated user with Subscriber-level permissions to export the entire database, including sensitive data like hashed administrator passwords.

MitigationUpdate the plugin to version 4.9.3 or later, which includes proper capability checks on the export_db function. Until then, restrict or disable user registration on the site.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Confirm WP BASE Booking plugin is installed
    Navigate to WordPress admin > Plugins and locate the WP BASE Booking plugin in the list of active or installed plugins
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    Click on the plugin in the WordPress plugins list to view its version number, or inspect the plugin header in wp-content/plugins/[plugin-folder]/index.php
    Affected if The version number is lower than 4.9.3 or cannot be determined (indicating an unpatched version)
  3. Check if WordPress user registration is enabled
    Go to WordPress Settings > General and look for the Membership option labeled 'Anyone can register' - verify whether it is checked
    Affected if User registration is enabled, allowing creation of Subscriber-level accounts
  4. Audit existing user accounts with Subscriber role
    Navigate to WordPress admin > Users > All Users and review the list for users assigned the Subscriber role
    Affected if There are Subscriber-level accounts present, especially ones you do not recognize or that were created recently
  5. Search for unexpected database export files
    Inspect the wp-content/uploads directory and any custom export folders for unfamiliar .sql, .csv, .json, or .db files that may have been created recently
    Affected if Unknown database export files exist on the server that were not created by an administrator

You are affected if the WP BASE Booking plugin is installed with a version below 4.9.3 AND user registration is enabled, allowing any subscriber-level user to export the database via the vulnerable export_db function.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 4.9.3 or later, which includes proper capability checks on the export_db function. Until then, restrict or disable user registration on the site.

Recommended fix Moderate confidence

4.9.3 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WP BASE Booking of Appointments, Services and Events'
  4. Click 'Update now' if an update is available, or manually upload the latest version from wordpress.org/plugins/wp-base-booking
  5. After update, verify the version is higher than 4.9.2

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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