dbcve.org
BuddypressWordPress extension

CVE-2024-10011

HIGH · 8.1 CVSS v3.1 Published 2024-10-25
Fix available
A fix is available. Upgrade to after 14.1.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
The BuddyPress plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 14.1.0 via the id parameter. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform actions on files outside of the originally intended directory and enables file uploads to directories outside of the web root. Depending on server configuration it may be possible to upload files with double extensions.

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 confidence

The BuddyPress WordPress plugin before version 14.1.1 contains a directory traversal vulnerability via the id parameter. Authenticated attackers with Subscriber-level access can manipulate the id parameter to traverse directories outside the intended path and upload files with double extensions to directories outside the web root, potentially leading to remote code execution depending on server configuration.

MitigationUpdate BuddyPress to version 14.1.1 or later. Additionally, restrict subscriber-level user upload capabilities, implement WAF rules to detect directory traversal patterns, and configure the server to prevent execution of uploaded files.

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
BuddypressWordPress extension
Affected:<= 14.1.0

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed BuddyPress version
    In WordPress admin, go to Plugins > Installed Plugins and look for BuddyPress to see the version number, or check the plugin file header in wp-content/plugins/buddypress/bp-loader.php
    Affected if The installed version is 14.1.0 or lower (any version <= 14.1.0)
  2. Verify the upload functionality is accessible
    Check if the BuddyPress upload feature is enabled by examining the plugin settings at BuddyPress > Settings > Component Setup, looking for the Activity component or similar upload-related components
    Affected if The Activity component or upload-related BuddyPress components are enabled
  3. Confirm subscriber-level user accounts exist
    In WordPress admin, go to Users > All Users and check if any users with the Subscriber role exist, or query the wp_usermeta table for users with wp_capabilities containing 'subscriber'
    Affected if There is at least one user with Subscriber role (or any authenticated user can access)
  4. Inspect server upload directory configuration
    Check the wp-content/uploads directory and server configuration (Apache .htaccess or Nginx config) to see if files uploaded via BuddyPress are stored in a web-accessible location
    Affected if Uploaded files are stored within the web root in a directory that permits file execution

You are affected if BuddyPress version is 14.1.0 or lower AND the upload functionality is enabled AND at least one subscriber-level user exists AND uploaded files are accessible via the web server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 14.1.0
Interim mitigation

Update BuddyPress to version 14.1.1 or later. Additionally, restrict subscriber-level user upload capabilities, implement WAF rules to detect directory traversal patterns, and configure the server to prevent execution of uploaded files.

Recommended fix High confidence

BuddyPress 14.2.0 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find BuddyPress in the plugin list
  4. Click 'Update Now' if an update is available, or manually download the latest version from wordpress.org/plugins/buddypress/
  5. After updating, verify the version number shows 14.2.0 or higher in the Plugins list
  6. Test that BuddyPress functionality (activity streams, member profiles, groups) works correctly
Caveat Review BuddyPress 14.2.0 release notes for any template changes or deprecated features before updating on production sites

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Buddypress Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10011 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10011 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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