BuddyPress <= 9.0.0 - Information Disclosure via REST API
Strategic Overview
- Status
- Patched in 9.1.1
- Affected Plugin
- BuddyPress
- Affected Version
<= 9.0.0- CVSS
- 8.8High
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE pending
At a glance
This record tracks a high-severity Incorrect Authorization vulnerability in the BuddyPress WordPress plugin, affecting versions <= 9.0.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 9.1.1; sites on affected versions should update now. Disclosed August 2021, reported by Brajesh Singh.
Vulnerability Overview
The BuddyPress plugin for WordPress is vulnerable to information disclosure via REST API in versions up to, and including 9.0.0. This is due to the plugin disclosing the activation key from responses of the create_item method in the BP REST API Signup controller. This makes it possible for non-privileged attackers to obtain administrator rights by exploiting an issue in the REST API members endpoint.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-863: Incorrect Authorization
Reaching this weakness in BuddyPress <= 9.0.0 takes a caller who can reach the endpoint. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For BuddyPress the fix is 9.1.1: builds <= 9.0.0 are affected, anything from 9.1.1 onward is not.
Remediation
Update to version 9.1.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: BuddyPress 9.1.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in BuddyPress
- 10.0BuddyPress 2.0 - 2.7.3 Arbitrary File Deletion
- 9.8BuddyPress <= 9.0.0 SQL Injection
- 9.8CVE-2012-2109: BuddyPress - 1.5-1.5.4 SQL Injection
CVE-2012-2109 - 8.8BuddyPress <= 7.2.1 Insufficient Privilege De-escalation
- 8.8BuddyPress <= 2.3.4 Privilege Escalation
- 8.1CVE-2024-10011: BuddyPress <= 14.1.0 Directory Traversal
CVE-2024-10011 - 7.5CVE-2026-1360: BuddyPress <= 14.5.0 PHP Object Injection
CVE-2026-1360 - 7.5CVE-2020-5244: BuddyPress <= 5.1.1 Sensitive Information Disclosure
CVE-2020-5244
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C