Multi Purpose Mail FormWordPress extension · Lindeni
CVE-2024-50526
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 · uneditedUnrestricted 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 confidenceThe Multi Purpose Mail Form plugin for WordPress contains an unrestricted file upload vulnerability (CWE-434) in versions through 1.0.2. The plugin fails to properly validate uploaded file types, allowing attackers to upload malicious PHP files (web shells) that can be executed for remote code execution on the server.
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
Multi Purpose Mail FormWordPress extension
<= 1.0.2CVSS 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 plugin installationNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Lindeni Multi Purpose Mail Form' or check the plugins directory (/wp-content/plugins/) for a folder named similarlyAffected if The plugin is present in the WordPress installation
-
Identify installed versionIn WordPress plugins list, find the plugin and view the version number under the plugin name; alternatively, read the main plugin PHP file header for the 'Version' fieldAffected if Version is 1.0.2 or lower
-
Confirm upload functionality exposureCheck for frontend forms that use the plugin's upload feature; examine plugin settings or shortcodes for any file input fields; test submitting a file to any public-facing formAffected if The plugin provides a file upload form that is accessible on the website
-
Inspect upload directoryCheck wp-content/uploads/ directory for any PHP files or scripts; review .htaccess or config files for script execution permissions on upload foldersAffected if PHP files exist in upload directories or script execution is allowed in upload folders
-
Look for web shell indicatorsSearch upload directories for unusual PHP files with random names, encoded content, or base64 strings; check access logs for requests to PHP files in /uploads/Affected if Suspicious PHP files are found in upload directories or were recently accessed
If the Lindeni Multi Purpose Mail Form plugin version 1.0.2 or lower is installed AND its file upload feature is exposed on the site, the environment is affected by this vulnerability.
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 dataImplement strict allowlist-based file type validation (extension and MIME type), store uploads outside the webroot or with randomized names, disable script execution permissions on upload directories, and remove any publicly accessible upload handlers.
Fix this in Multi Purpose Mail Form
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50526 — 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-50526 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