CVE-2024-10547
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 · uneditedThe WP Membership plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the user_profile_image_upload() function in all versions up to, and including, 1.6.2. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
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 confidenceThe WP Membership plugin for WordPress lacks file type validation in its user_profile_image_upload() function, allowing unauthenticated attackers to upload arbitrary files to the server. This arbitrary file upload vulnerability enables remote code execution on affected sites running versions up to and including 1.6.2.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Membership plugin is installedCheck the WordPress plugins directory or access Plugins > Installed Plugins in the WordPress admin dashboard. Look for an entry named 'WP Membership' or 'WP Membership by [developer]'.Affected if The plugin is not installed on the WordPress site.
-
Determine the installed plugin versionIn the WordPress admin, go to Plugins > Installed Plugins and locate the WP Membership entry. The version number is displayed below the plugin name. Alternatively, inspect the plugin's main PHP file header or check via wp-cli: wp plugin list --name='wp-membership'Affected if The displayed version is 1.6.2 or lower.
-
Confirm the plugin is activeIn WordPress admin > Plugins > Installed Plugins, verify that WP Membership shows as 'Active' (not deactivated or missing). You can also use wp-cli: wp plugin status wp-membershipAffected if The plugin is currently activated on the site.
-
Check for unauthorized uploaded filesInspect the WordPress uploads directory (typically wp-content/uploads/) for any suspicious files with extensions such as .php, .phtml, .php5, .php7, .js, or .htaccess that were uploaded unexpectedly. Check file modification timestamps around the time the plugin was active.Affected if Unexpected script files exist in upload directories that were not intentionally placed there.
You are affected if the WP Membership plugin is installed, active, and running version 1.6.2 or lower.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the WP Membership plugin to a version beyond 1.6.2 that includes proper file type validation and upload restrictions, or disable the plugin until a patch is available. Consider implementing web application firewall rules to block suspicious file uploads as an interim measure.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10547 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10547 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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