BP Profile Search <= 5.7.5 - Cross-Site Request Forgery to Reflected Cross-Site Scripting
Strategic Overview
- Status
- Patched in 5.8
- Affected Plugin
- BP Profile Search
- Affected Version
<= 5.7.5- CVSS
- 6.1Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-7850
At a glance
CVE-2024-7850 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the BP Profile Search WordPress plugin, affecting versions <= 5.7.5. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.8; sites on affected versions should update now. Disclosed August 2024, reported by vgo0.
Vulnerability Overview
The BP Profile Search plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.7.5. This is due to missing or incorrect nonce validation on the bps_ajax_field_selector(), bps_ajax_template_options(), and bps_ajax_field_row() functions. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
BP Profile Search <= 5.7.5 carries this weakness at bps_ajax_field_selector(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For BP Profile Search the fix is 5.8: builds <= 5.7.5 are affected, anything from 5.8 onward is not.
Remediation
Update to version 5.8, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to BP Profile Search: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: BP Profile Search 5.8 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in BP Profile Search
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C