dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-50484

CRITICAL · 10.0 CVSS v3.1 Published 2024-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Lindeni Mahlalela Multi Purpose Mail Form multi-purpose-mail-form allows Upload a Web Shell to a Web Server.This issue affects Multi Purpose Mail Form: from n/a through <= 1.0.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 · moderate confidence

The Multi Purpose Mail Form plugin for WordPress contains an unrestricted file upload vulnerability (CWE-434) that allows unauthenticated attackers to upload arbitrary PHP files, including web shells, directly to the web server. This grants attackers remote code execution capability and full server compromise.

MitigationUpgrade to the latest version of the plugin immediately. If no patch exists, disable and remove the plugin. Implement server-side file type validation, rename uploaded files to non-executable extensions, store uploads outside the web root, and disable script execution in upload directories.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 Multi Purpose Mail Form plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins. Look for 'Multi Purpose Mail Form' or similar naming. Alternatively, check the /wp-content/plugins/ directory for folders containing 'multi-purpose-mail-form', 'mpmf', 'mp-mail-form', or similar variations.
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find the Multi Purpose Mail Form plugin and read the version number from the plugin description. Compare this against any version guidance from the plugin vendor or security advisories.
    Affected if The installed version is lower than the patched version released after this CVE
  3. Verify the upload directory is accessible via web
    Check the plugin's settings for the upload path configuration. Common paths include /wp-content/uploads/mpmf/, /wp-content/uploads/, or custom paths. Attempt to access this directory via HTTP (e.g., curl http://example.com/wp-content/uploads/mpmf/) to confirm it is web-accessible.
    Affected if The upload directory is within the web root and directly accessible via HTTP
  4. Inspect upload directory for suspicious PHP files
    List all files in the configured upload directory (e.g., ls -la /wp-content/uploads/mpmf/ or via FTP/SFTP). Look for unexpected .php, .phtml, .php5, .phar, or other executable extensions. Check file creation dates for recent unauthorized uploads.
    Affected if Unexpected PHP files or other executable scripts exist in the upload directory
  5. Review web server access logs for file upload requests
    Search web server logs (Apache access.log, Nginx access.log) for POST requests to the plugin's upload handler endpoint. Look for requests to paths like /wp-json/mpmf/v1/upload, /?action=mpmf_upload, or similar. Check for unusual file extensions in the requests.
    Affected if There are POST requests to upload endpoints with .php or other executable file extensions
  6. Check if the plugin upload functionality is exposed without authentication
    Review the plugin's configuration to determine if file uploads require authentication. Attempt a test upload request without authentication headers to see if it is accepted.
    Affected if The upload endpoint accepts and processes requests without requiring authentication

A defender is affected if the Multi Purpose Mail Form plugin is installed, the upload directory is web-accessible, and especially if unauthorized PHP files are present in upload directories or suspicious upload requests appear in logs.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the latest version of the plugin immediately. If no patch exists, disable and remove the plugin. Implement server-side file type validation, rename uploaded files to non-executable extensions, store uploads outside the web root, and disable script execution in upload directories.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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