Description
The BP Profile Search plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 5.9 via the 'ajax_template' value parsed from the client-controlled 'bps_directory' cookie during BuddyPress AJAX directory requests. The bps_directory_ajax() filter (hooked onto bp_legacy_object_template_path and bp_nouveau_object_template_path) reads the cookie, applies only a referer-derived 'page' comparison in bps_get_directory_data() (where bps_current_page() uses HTTP_REFERER during AJAX and is therefore also attacker-controlled), and then suffixes the attacker-controlled template value with '.php' and passes it to bp_locate_template() with no basename restriction, no whitelist, and no path-traversal check. This makes it possible for unauthenticated attackers to include arbitrary PHP files on the server, which can lead to remote code execution when PHP files can be uploaded or when images such as the default wordpress:php8.
References6
- plugins.trac.wordpress.org/browser/bp-profile-search/tags/5.9/b…
- plugins.trac.wordpress.org/browser/bp-profile-search/tags/5.9/b…
- plugins.trac.wordpress.org/browser/bp-profile-search/tags/5.9/b…
- plugins.trac.wordpress.org/browser/bp-profile-search/tags/6.0/b…
- plugins.trac.wordpress.org/changeset/3737650
- www.wordfence.com/threat-intel/vulnerabilities/id/a35419ff-a342…
Metrics
- CVSS 3.1
-
8.1
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 1% percentile: 66 · as of 11 November 2026
- CWE
- CWE-98
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.