dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-53673

HIGH · 8.1 CVSS v3.1 Published 2026-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
BuddyPress 14.4.0 contains an insecure direct object reference vulnerability in the messages REST API that allows authenticated attackers to access arbitrary private message threads by supplying a user_id parameter in the request. Attackers can pass another user's identifier to the get_item_permissions_check method, which validates the supplied user_id instead of the logged-in user and is reused by the update and delete handlers, to read, reply to, or delete any user's private messages.

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 · high confidence

BuddyPress 14.4.0 has an IDOR vulnerability in its messages REST API where the get_item_permissions_check method validates the attacker-supplied user_id parameter instead of the authenticated user's identity. This allows any authenticated user to read, reply to, or delete private messages belonging to other users by manipulating the user_id parameter in requests.

MitigationApply vendor patches when available; until then, restrict access to the messages REST API endpoints or implement WAF rules to block requests with mismatched user_id parameters.

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify BuddyPress version
    Check the installed BuddyPress version by inspecting the main plugin file (buddypress.php) or through the WordPress admin dashboard under Plugins. Look for the version constant or header.
    Affected if The installed version is exactly 14.4.0
  2. Confirm Messages REST API is enabled
    Test access to the BuddyPress Messages REST API endpoint (typically /wp-json/bp/v1/messages) using an authenticated HTTP request with valid user credentials.
    Affected if The REST API endpoint responds successfully, indicating it is enabled and accessible
  3. Inspect get_item_permissions_check method
    Locate the file containing the get_item_permissions_check method in the BuddyPress messages component (usually in bp-messages/classes/class-bp-messages-rest-actions.php or similar). Examine the code to verify whether it validates against the authenticated user's ID or the user-supplied user_id parameter.
    Affected if The code validates against the user-supplied user_id parameter instead of the authenticated user's identity (e.g., uses $request->get_param('user_id') rather than get_current_user_id())
  4. Test for IDOR vulnerability
    Using an authenticated session for User A, send a REST API request to read/reply/delete a private message belonging to User B by supplying user_id parameter pointing to User B's identifier. Observe if the operation succeeds when it should be denied.
    Affected if The API allows User A to access User B's private messages by supplying another user_id, confirming the IDOR vulnerability is present

A user is affected if they have BuddyPress 14.4.0 installed with the Messages REST API enabled, and the get_item_permissions_check method validates against the user-supplied user_id rather than the authenticated user's identity.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches when available; until then, restrict access to the messages REST API endpoints or implement WAF rules to block requests with mismatched user_id parameters.

Recommended fix Moderate confidence

BuddyPress 14.4.1 or latest stable release

  1. Check your current BuddyPress version in WordPress admin under Plugins > Installed Plugins
  2. Backup your WordPress database and files before updating
  3. Update BuddyPress to the latest available version through WordPress admin (Plugins > Add New > Upload or WordPress updates)
  4. Verify the update was successful and test that the messages REST API now properly validates the authenticated user

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53673 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53673 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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