CVE-2024-0972 json
BuddyPress Members Only <= 3.4.8 - Improper Access Control to Sensitive Information Exposure via REST API
published 2y ago modified 5mo ago also EUVD-2024-16749
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
The BuddyPress Members Only plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.4.9 via the REST API. This makes it possible for unauthenticated attackers to bypass the plugin's "All Other Sections On Your Site Will be Opened to Guest" feature (when unset) and view restricted page and post content.
Is CVE-2024-0972 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- zhuyi BuddyPress Members Only
- zhuyi buddypress_members_only
Classification
- Weakness
- Technology feeds
References
-
wordfence.com
/threat-intel/vulnerabilities/id/dcfead67-d75d-46ae-ac68-a34643ac2f52?source=cve
third-party-advisory
-
plugins.trac.wordpress.org
/browser/buddypress-members-only/trunk/buddypress-members-only.php#L682
product
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3122096%40buddypress-members-only&new=3122096%40buddypress-memb
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3128839%40buddypress-members-only&new=3128839%40buddypress-memb
Sources
- CVE List CVE-2024-0972
- NVD CVE-2024-0972
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.