CVE-2024-3295
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 User Registration – Custom Registration Form, Login Form, and User Profile WordPress Plugin plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the profile_pic_remove function in versions up to, and including, 3.1.5. This makes it possible for unauthenticated attackers to delete any media file.
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 confidenceThis is a broken access control vulnerability in the User Registration WordPress plugin. The profile_pic_remove function lacks a WordPress capability check (like current_user_can()), allowing any unauthenticated visitor to delete arbitrary media files by passing a media ID to the function. This is an IDOR combined with missing authorization, enabling unauthorized data deletion.
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
-
Confirm User Registration plugin is installedNavigate to Plugins > Installed Plugins in WordPress admin, or inspect /wp-content/plugins/user-registration/ directory via file manager or SSH. Check the plugin main file header for the Version field.Affected if The User Registration plugin is present in the environment
-
Identify the installed versionRead the version number from the plugin header in user-registration.php or from the WordPress plugins admin page. The version typically appears as 'Version: x.x.x' in the plugin comments.Affected if The installed version is lower than 3.1.6 (for example, 3.1.5, 3.1.4, etc.)
-
Verify the profile_pic_remove function lacks capability checksInspect the plugin file containing profile_pic_remove (typically in includes/functions-ur-profile.php or similar). Search for the function definition and verify whether current_user_can() or a capability check is present before executing the media deletion logic.Affected if The function exists and contains no current_user_can() or similar authorization check before processing the media ID
-
Test if the AJAX endpoint responds to unauthenticated requestsSend a POST request to /wp-admin/admin-ajax.php with action=profile_pic_remove and a media_id parameter (for example: curl -X POST https://your-site.com/wp-admin/admin-ajax.php -d 'action=profile_pic_remove&media_id=1'). A successful 200 response without authentication indicates the vulnerability is present.Affected if The endpoint accepts the request and returns a successful response without requiring authentication
The environment is affected if the User Registration plugin is installed with a version lower than 3.1.6 and the profile_pic_remove AJAX endpoint accepts unauthenticated requests to delete media files.
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 User Registration plugin to version 3.1.6 or later which includes proper capability verification for the profile_pic_remove function. Until patched, consider disabling the plugin or adding WAF rules to block unauthorized media deletion requests.
- Consultation1.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 $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3295 — 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-3295 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