dbcve.org
Buddypress CoverWordPress extension · Buddypress Cover Project

CVE-2024-35746

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to after 2.1.4.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Unrestricted Upload of File with Dangerous Type vulnerability in Asghar Hatampoor BuddyPress Cover allows Code Injection.This issue affects BuddyPress Cover: from n/a through 2.1.4.2.

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 Cover plugin through version 2.1.4.2 contains an unrestricted file upload vulnerability that allows attackers to upload files with dangerous types (e.g., executable PHP files) without proper validation, leading to code injection and potential remote code execution.

MitigationImmediately restrict file uploads to safe types only (images), validate file content/MIME type server-side, rename uploaded files, disable script execution in the upload directory, and consider blocking the plugin at the web server level until an official patch is available.

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
Buddypress CoverWordPress extension
Affected:<= 2.1.4.2

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Identify if Buddypress Cover plugin is installed
    Locate the plugin directory in your WordPress installation at wp-content/plugins/ and look for a folder containing 'buddypress-cover' or similar. Alternatively, access your WordPress admin dashboard and navigate to Plugins > Installed Plugins to find 'Buddypress Cover' or 'Buddypress Cover Project'.
    Affected if The plugin is found in the plugins directory or listed in the WordPress admin plugins list.
  2. Determine the installed plugin version
    Open the main plugin file (usually named plugin-name.php in the plugin folder) and locate the version comment or header at the top of the file. Alternatively, in WordPress admin, click on the plugin to view its details and note the version number displayed.
    Affected if The installed version is 2.1.4.2 or any lower version number.
  3. Verify if the plugin upload functionality is accessible
    Check if users with upload permissions (such as members or authors) can access the BuddyPress member profile upload feature. Inspect the plugin settings in WordPress admin under BuddyPress settings to confirm the cover image upload functionality is enabled.
    Affected if The plugin is active and the cover image upload feature is enabled for user profiles.
  4. Inspect the upload directory configuration
    Check the wp-content/uploads/ directory and any buddypress/ subdirectory for permissions. Look for .htaccess or web.config files that should block script execution. Verify that uploaded files retain their original extensions rather than being renamed to safe extensions.
    Affected if The upload directory allows script execution or does not rename uploaded files to non-executable extensions.

Your environment is affected if the Buddypress Cover plugin is installed, active, and running at version 2.1.4.2 or lower, with the upload feature enabled for users.

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 2.1.4.2
Interim mitigation

Immediately restrict file uploads to safe types only (images), validate file content/MIME type server-side, rename uploaded files, disable script execution in the upload directory, and consider blocking the plugin at the web server level until an official patch is available.

Recommended fix Moderate confidence

Latest version of BuddyPress Cover (verify version number on WordPress plugin repository is greater than 2.1.4.2)

  1. 1. Check current BuddyPress Cover plugin version installed on the WordPress site
  2. 2. Backup the WordPress database and files before making changes
  3. 3. Navigate to Plugins > All Plugins in WordPress admin dashboard
  4. 4. Locate BuddyPress Cover plugin and update to the latest available version
  5. 5. Verify the update was successful and the plugin is functioning correctly after upgrade
  6. 6. Review any uploaded cover images to ensure no malicious files were uploaded prior to the fix

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

Fix this in Buddypress Cover Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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