BuddyPress lets subscribers alter other users' notifications
BuddyPress through 14.3.3 accepts a user-controlled key in bp_notifications_action_bulk_manage without validating that the referenced notification belongs to the caller. An authenticated Subscriber can delete another user's notifications or mark them read or unread. The authoritative export identifies the action and vulnerable key but does not disclose the request route or parameter name carrying the key.
- Component
- BuddyPress
- Plugin slug
buddypress- Affected
- <= 14.3.3
- Safe version
- See mitigation notes
- Published
- Sep 11, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Sep 11, 2026 and is one of 18 known issues for this plugin.
Update, patch or deactivate.
The authoritative export does not identify the first fixed release. Obtain a vendor-confirmed update after 14.3.3 and ensure bp_notifications_action_bulk_manage verifies ownership of every notification identifier before deleting it or changing its read state. Review unexpected notification changes where practical.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The BuddyPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 14.3.3 via the bp_notifications_action_bulk_manage due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete/mark as read/mark as unread notifications of other users.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N