CVE-2026-39587
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 · uneditedUnauthenticated Privilege Escalation in WP BASE Booking <= 5.9.0 versions.
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 confidenceThis is an unauthenticated privilege escalation vulnerability in the WP BASE Booking WordPress plugin affecting versions 5.9.0 and below. An attacker without any authentication can exploit this to gain elevated privileges (likely administrator-level) on the WordPress 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WP BASE Booking plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'WP BASE Booking' in the list of active plugins.Affected if The plugin is present and active in the WordPress installation
-
Identify the installed version of WP BASE BookingIn the Plugins list, click on 'WP BASE Booking' to view plugin details, or check the plugin header comment in wp-content/plugins/wp-base-booking/index.php for the Version field.Affected if The version number is 5.9.0 or lower
-
Review WordPress user accounts for unauthorized administrator accountsNavigate to Users > All Users in the WordPress admin panel. Check for any administrator-level accounts that were not created by known site administrators, paying attention to recently added users with unfamiliar usernames or email addresses.Affected if There are administrator accounts that were not created by legitimate site administrators
-
Check for suspicious PHP files in the plugin directoryUsing a file manager or FTP, examine wp-content/plugins/wp-base-booking/ for any recently created or modified PHP files, especially in subdirectories, that were not part of the original plugin installation.Affected if Unexpected PHP files exist in the plugin directory that were not installed by the plugin maintainer
A user is affected if the WP BASE Booking plugin is installed with version 5.9.0 or below, since the vulnerability allows unauthenticated attackers to create administrative accounts
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.
From vendor dataUpdate WP BASE Booking plugin to a version newer than 5.9.0. If immediate update is not possible, consider disabling the plugin or implementing web application firewall rules to block exploitation attempts.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39587 — 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-2026-39587 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