CVE-2026-42736
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 · uneditedAuthorization Bypass Through User-Controlled Key vulnerability in wordplus BP Better Messages bp-better-messages allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects BP Better Messages: from n/a through <= 2.14.16.
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 confidenceAuthorization bypass vulnerability in BP Better Messages plugin where an attacker can manipulate a user-controlled key to bypass access control checks. The plugin incorrectly trusts user-supplied input for authorization decisions, allowing unauthorized access to privileged functionality.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if BP Better Messages plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'BP Better Messages', or check the filesystem at /wp-content/plugins/bp-better-messages/ for the main plugin fileAffected if The plugin is not installed on the WordPress site
-
Check installed plugin versionView the plugin header in /wp-content/plugins/bp-better-messages/bp-messages.php or access it via Plugins page in WordPress adminAffected if Version is lower than 2.14.17 (vulnerable versions: any version before the fix)
-
Verify BP Better Messages functionality is activeCheck if the plugin is activated in WordPress admin and if BuddyPress messaging features are enabled in plugin settingsAffected if The plugin is activated and users can access the messaging system, enabling the vulnerable authorization logic to be reachable
-
Identify if user-controlled keys are used in authorizationReview custom code or hooks added to theme/functions.php that may interact with BP Better Messages authorization; grep for 'bp_messages' and 'capabilities' or 'current_user_can' calls that rely on user-supplied parametersAffected if Custom code passes user-controlled input (like message IDs, user IDs from URL/query params) directly into authorization checks without validation
User is affected if BP Better Messages plugin is installed with version lower than 2.14.17 and the messaging functionality is active, allowing user-supplied input to influence access control decisions.
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 BP Better Messages plugin to version 2.14.17 or later which should contain the fix. Alternatively, review and refactor the authorization logic to not rely on user-controlled keys for access control decisions.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42736 — 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-42736 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