Quick answers
- Is CVE-2026-53673 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53673 being exploited in the wild.
- How severe is CVE-2026-53673?
- High severity, with a CVSS score of 8.1, published 10 June 2026.
- Which products and versions are affected?
- BuddyPress <= 14.4.0, 14.4.0; buddypress/buddypress (Packagist) < 14.5.0, ECOSYSTEM:introduced=0,fixed=14.5.0.
- Is there a fix for CVE-2026-53673?
- Yes. buddypress/buddypress (Packagist): upgrade to 14.5.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53673 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53673?
- Check whether you run BuddyPress or buddypress/buddypress (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- buddypress/buddypress (Packagist): upgrade to 14.5.0 or later
composer require buddypress/buddypress:^14.5.0
Technical details
An Insecure Direct Object Reference (IDOR) vulnerability exists in the BuddyPress messages REST API due to improper validation in the get_item_permissions_check method. The method incorrectly validates a user-supplied user_id parameter instead of the identity of the currently logged-in user. Because this permission check is reused by update and delete handlers, an authenticated attacker can provide an arbitrary user's ID to read, reply to, or delete their private message threads. The vulnerability is addressed in version 14.5.0.
Affected products
- BuddyPress BuddyPress 14.4.0
Identifiers
- CVE-2026-53673
- GHSA-j3j5-5m8v-7gvc
Timeline
- 2026-06-10: disclosed
- 2026-06-10: advisory
- 2026-08-12: patched: Advisory updated to reflect patch availability in 14.5.0