CVE-2024-32960
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 · uneditedImproper Privilege Management vulnerability in Booking Ultra Pro allows Privilege Escalation.This issue affects Booking Ultra Pro: from n/a through 1.1.12.
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 confidenceBooking Ultra Pro plugin for WordPress contains an improper privilege management vulnerability allowing authenticated users to escalate their privileges beyond what their role should permit. The specific mechanism is not detailed, but such flaws typically involve insufficient validation of user capabilities or role assignments.
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.
-
Confirm Booking Ultra Pro plugin is installedAccess WordPress admin dashboard and navigate to Plugins > Installed Plugins, or check for the presence of /wp-content/plugins/booking-ultra-pro/ directory via file system inspectionAffected if The Booking Ultra Pro plugin appears in the installed plugins list
-
Identify the installed version of Booking Ultra ProIn WordPress admin, find the plugin in Plugins > Installed Plugins and note the version number displayed beneath the plugin name, or read the version from the plugin's main PHP file headerAffected if The installed version cannot be determined or is older than the patched version
-
Review user accounts with elevated rolesNavigate to Users > All Users in WordPress admin and examine the role assigned to each user account, noting any users assigned Administrator or other high-privilege roles unexpectedlyAffected if Any user account has been assigned a role higher than what they should legitimately possess, or unexpected users have Administrator capabilities
-
Check for unauthorized capability assignmentsUse a user role editor plugin or query the wp_usermeta table to inspect capabilities assigned to non-administrator users, looking for capabilities like manage_options, edit_users, or delete_usersAffected if Non-administrator users possess administrative-level capabilities they should not have
-
Audit recent role or privilege changesReview WordPress activity logs, server access logs, or audit trails for events involving user role modifications, capability changes, or privilege escalation actions occurring recentlyAffected if Recent activity shows role or capability modifications that were not performed by a legitimate administrator
A user is affected if Booking Ultra Pro is installed and any user account possesses privileges beyond what their assigned role should permit, or unauthorized role changes have occurred.
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 to a patched version of Booking Ultra Pro when available, or review and restrict the plugin's role and capability assignments to enforce proper privilege boundaries.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-32960 — 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-32960 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