CVE-2025-67953
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 · uneditedIncorrect Privilege Assignment vulnerability in Booking Activities Team Booking Activities booking-activities allows Privilege Escalation.This issue affects Booking Activities: from n/a through <= 1.16.44.
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 confidenceAn Incorrect Privilege Assignment vulnerability in the Booking Activities WordPress plugin (versions up to 1.16.44) allows authenticated users to access functionality or data beyond their intended privilege level, enabling privilege escalation.
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.
-
Identify if Booking Activities plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Booking Activities', or check the file /wp-content/plugins/booking-activities/readme.txt for the Version lineAffected if Plugin is present on the system
-
Determine the installed plugin versionView the plugin version in WordPress admin Plugins page, or inspect the 'Version:' field in /wp-content/plugins/booking-activities/readme.txt or in the plugin header comment in the main PHP fileAffected if Version is 1.16.44 or lower (any version up to and including 1.16.44)
-
Confirm the plugin is activeCheck the Plugins admin page to see if Booking Activities is activated, or query the WordPress options table for the option 'booking_activities_version' with status 'active'Affected if Plugin version <= 1.16.44 AND plugin is currently active
-
Verify authenticated user access existsReview the WordPress Users admin page to confirm at least one user account exists with any role (subscriber, contributor, author, editor, or administrator)Affected if Plugin version <= 1.16.44 AND plugin is active AND at least one authenticated user account exists in WordPress
The environment is affected if Booking Activities plugin version 1.16.44 or lower is installed and active with any user accounts present, allowing privilege escalation for authenticated users.
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 dataUpgrade Booking Activities to version 1.16.45 or later which contains the security fix, or implement proper capability checks on all user actions within the plugin.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67953 — 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-2025-67953 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