BuddyPress <= 14.1.0 - Authenticated (Subscriber+) Directory Traversal
Strategic Overview
- Status
- Patched in 14.2.1
- Affected Plugin
- BuddyPress
- Affected Version
<= 14.1.0- CVSS
- 8.1High
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2024-10011
At a glance
CVE-2024-10011 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the BuddyPress WordPress plugin, affecting versions <= 14.1.0. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high confidentiality, integrity impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 14.2.1; sites on affected versions should update now. Disclosed October 2024, reported by Dominik Dziura (Domons).
Vulnerability Overview
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 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.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in BuddyPress <= 14.1.0 takes an account at Subscriber level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For BuddyPress the fix is 14.2.1: builds <= 14.1.0 are affected, anything from 14.2.1 onward is not.
Remediation
Update to version 14.2.1, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: BuddyPress 14.2.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in BuddyPress
- 9.8BuddyPress <= 9.0.0 SQL Injection
- 9.8CVE-2012-2109: BuddyPress - 1.5-1.5.4 SQL Injection
CVE-2012-2109 - 8.8BuddyPress <= 9.0.0 Information Disclosure via REST API
- 8.8BuddyPress <= 7.2.1 Insufficient Privilege De-escalation
- 8.8CVE-2021-21389: BuddyPress 5.0.0-7.2.0 Privilege Escalation
CVE-2021-21389 - 8.8BuddyPress <= 2.3.4 Privilege Escalation
- 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