CVE-2026-59541
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 · uneditedSubscriber Privilege Escalation in WP BASE Booking <= 6.3.1 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 a privilege escalation vulnerability in the WP BASE Booking WordPress plugin where authenticated users with subscriber-level permissions can elevate their privileges beyond what that role should allow. The plugin fails to properly enforce capability checks, allowing subscribers to perform administrative or higher-privileged actions.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify WP BASE Booking plugin is installedNavigate to WordPress Admin > Plugins and look for 'WP BASE Booking' in the installed plugins list. Note whether it is active or inactive.Affected if The plugin is installed and active, indicating the vulnerable code could be executed.
-
Determine installed plugin versionIn the Plugins list, click on the plugin details link for WP BASE Booking or hover over the plugin name to reveal the version number displayed beneath the plugin title.Affected if The version is 6.3.1 or any earlier version number (e.g., 6.3.0, 6.2.9, etc.).
-
Compare version against affected rangeCompare the installed version you found against the affected range: versions 6.3.1 and earlier. If your version falls within or below 6.3.1, the vulnerability is potentially present.Affected if Installed version is 6.3.1 or lower.
-
Review Administrator-level user accountsGo to WordPress Admin > Users and examine the list of users with Administrator role. Check for any accounts you do not recognize, especially those created recently or with suspicious usernames.Affected if There are unrecognized Administrator accounts present that were not created by known administrators.
-
Check user creation activity logsIf your WordPress has activity logging plugins or audit logs, review recent user creation events to see if any Administrator accounts were added by Subscriber-level users.Affected if Subscriber-level users have successfully created Administrator-level accounts.
You are affected if the WP BASE Booking plugin is installed with version 6.3.1 or earlier AND you find unauthorized Administrator accounts or evidence of privilege escalation in your user logs.
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 to a version newer than 6.3.1. Until the update is available, consider restricting or disabling subscriber accounts, or temporarily deactivating the plugin if the risk is unacceptable.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59541 — 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-59541 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