CVE-2024-2920
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-Members Membership Plugin plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 3.4.9.3 due to the plugin uploading user supplied files to a publicly accessible directory in wp-content without any restrictions. This makes it possible for unauthenticated attackers to view files uploaded by other users which may contain sensitive information.
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-Members Membership Plugin for WordPress versions up to 3.4.9.3 stores user-uploaded files in a publicly accessible wp-content directory without any access restrictions or authentication requirements. This allows any unauthenticated attacker to directly access files uploaded by other users, potentially exposing sensitive personal or private information contained in those files.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP-Members plugin is installedCheck the plugin directory for wp-members folder: look in wp-content/plugins/ for the wp-members directory, or check WordPress admin under Plugins > Installed Plugins for 'WP-Members Membership Plugin'Affected if The plugin is not installed on the WordPress site
-
Determine the installed WP-Members versionOpen wp-content/plugins/wp-members/readme.txt and locate the version number in the header, or check the plugin header in wp-content/plugins/wp-members/wp-members.phpAffected if The version is 3.4.9.3 or any earlier version (the vulnerability affects versions up to and including 3.4.9.3)
-
Identify the uploads directory used by the pluginCheck wp-content/uploads/ for any wp-members, member-upload, or similar subdirectories; also inspect the plugin settings in WordPress admin under WP-Members > Options > User Settings to locate the upload path configurationAffected if A custom upload directory is configured within wp-content and is publicly accessible via web browser
-
Confirm the uploads directory lacks access restrictionsAttempt to access the uploads directory directly via a web browser (e.g., navigate to yourdomain.com/wp-content/uploads/wpmembers/ or the configured upload path); verify there is no .htaccess file restricting access and no authentication required to view or download filesAffected if Directory listing is enabled or files can be downloaded without authentication by an unauthenticated user
A user is affected if WP-Members plugin version 3.4.9.3 or earlier is installed AND user-uploaded files are stored in a publicly accessible wp-content subdirectory without access controls.
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 dataRestrict file access by moving uploads outside the publicly accessible web root or implementing proper authentication and authorization checks before serving files. Additionally, implement file type validation and consider adding .htaccess rules or similar access controls to prevent unauthorized directory browsing and file retrieval.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2920 — 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-2920 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