CVE-2024-0972
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 · uneditedThe 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.
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 confidenceThe BuddyPress Members Only plugin for WordPress versions up to 3.4.9 contains a flaw in its REST API handling that allows unauthenticated attackers to bypass the access restriction feature. When the 'All Other Sections On Your Site Will be Opened to Guest' setting is not enabled, the plugin fails to properly enforce access controls on certain REST API endpoints, allowing unauthorized access to restricted page and post content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 3.3.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck your WordPress plugin directory for the BuddyPress Members Only plugin (typically in wp-content/plugins/) or look for it in the WordPress admin under Plugins > Installed PluginsAffected if The plugin named 'Membersonly Buddypress Members Only' or similar is present on the site
-
Check the installed plugin versionView the plugin details in WordPress admin (Plugins > Installed Plugins > Click on the plugin) or inspect the plugin header in its main PHP file to find the Version fieldAffected if The installed version is 3.3.5 or lower (versions up to and including 3.3.5 are affected)
-
Locate the plugin settingsNavigate to the plugin settings page in the WordPress admin dashboard. Look for a setting labeled 'All Other Sections On Your Site Will be Opened to Guest' or similar wordingAffected if This setting exists and is currently disabled or unchecked
-
Confirm the vulnerability conditionIf the plugin is installed with version 3.3.5 or lower AND the 'All Other Sections On Your Site Will be Opened to Guest' setting is disabled (not checked), the site is vulnerable to unauthenticated REST API access bypassAffected if All three conditions are true: plugin installed, version <= 3.3.5, and the bypass setting is disabled
Your environment is affected if the BuddyPress Members Only plugin version is 3.3.5 or lower and the 'All Other Sections On Your Site Will be Opened to Guest' setting is disabled, allowing unauthenticated REST API access to restricted content.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to BuddyPress Members Only version 3.5.0 or later, which contains the fix for this vulnerability. Alternatively, ensure the 'All Other Sections On Your Site Will be Opened to Guest' setting is enabled as a temporary workaround until the plugin can be updated.
3.4.9 or later
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find "BuddyPress Members Only" plugin
- Click "Update now" if an update is available, or manually upload version 3.4.9 or higher from the WordPress plugin repository
- Verify the plugin version after update to confirm upgrade was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0972 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0972 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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