dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-7850

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 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 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 · moderate confidence

The BP Profile Search WordPress plugin is vulnerable to Cross-Site Request Forgery (CSRF) in versions up to 5.7.5 due to missing or incorrect nonce validation on three AJAX functions: bps_ajax_field_selector(), bps_ajax_template_options(), and bps_ajax_field_row(). This allows unauthenticated attackers to forge administrative requests and inject malicious web scripts, provided they can trick a site administrator into clicking a malicious link.

MitigationUpdate to the latest version of BP Profile Search when available. Additionally, ensure all AJAX actions implement proper nonce verification using wp_verify_nonce() or check_admin_referer() before processing requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Confirm BP Profile Search plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for the bp-profile-search folder
    Affected if The plugin is present on the site
  2. Identify installed plugin version
    In WordPress admin, click on the BP Profile Search plugin to view details, or open the main plugin file (typically bp-profile-search.php) and locate the 'Version' header comment
    Affected if The version is 5.7.5 or any earlier version
  3. Verify plugin is active
    Check WordPress Plugins page to confirm BP Profile Search shows as 'Active'
    Affected if The plugin is enabled and running on the site
  4. Inspect AJAX function nonce handling
    Access the plugin source code and locate the functions bps_ajax_field_selector(), bps_ajax_template_options(), and bps_ajax_field_row(). Search for wp_verify_nonce(), check_admin_referer(), or nonce verification within these functions
    Affected if These three AJAX functions lack proper nonce validation (no wp_verify_nonce() or check_admin_referer() call found)
  5. Check admin AJAX hook registration
    Examine how the plugin registers its AJAX hooks (search for add_action('wp_ajax_...) calls) and verify if nonces are required for the affected endpoints
    Affected if The AJAX endpoints are accessible without requiring a valid nonce token

You are affected if BP Profile Search plugin version 5.7.5 or earlier is installed, active, and the vulnerable AJAX functions lack nonce verification, making administrative actions susceptible to CSRF attacks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of BP Profile Search when available. Additionally, ensure all AJAX actions implement proper nonce verification using wp_verify_nonce() or check_admin_referer() before processing requests.

Recommended fix Moderate confidence

BP Profile Search version 5.7.6 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the BP Profile Search plugin in the list
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, manually download the updated plugin from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is running version 5.7.6 or higher under Plugins > Installed Plugins

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7850 — 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-7850 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