Wp Mlm UnilevelWordPress extension · Wpmlmsoftware
CVE-2023-51475
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 IOSS WP MLM SOFTWARE PLUGIN.This issue affects WP MLM SOFTWARE PLUGIN: from n/a through 4.0.
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 MLM SOFTWARE plugin for WordPress contains an unrestricted file upload vulnerability (CWE-434) allowing attackers to upload dangerous file types without proper validation. This could enable remote code execution by uploading malicious scripts (e.g., PHP files) to the web 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
Wp Mlm UnilevelWordPress extension
<= 4.0CVSS 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.
-
Confirm WP MLM SOFTWARE plugin is installedAccess WordPress admin panel and navigate to Plugins > Installed Plugins to locate the plugin, or inspect the plugins directory for folders containing 'mlm' or 'unilevel' in the nameAffected if The plugin is present in the WordPress installation
-
Verify the plugin versionIn WordPress admin, view the plugin details page to read the version number, or open the main plugin PHP file and locate the Version header in the plugin comment blockAffected if The installed version is 4.0 or lower
-
Confirm file upload functionality is accessibleNavigate to the plugin settings or frontend pages where upload forms exist (typically in member registration, profile, or compensation plan assignment areas)Affected if The file upload feature is enabled and accessible to users or administrators
-
Check upload directory for dangerous filesExamine the uploads directory (default is wp-content/uploads/ or a custom path configured in the plugin) for files with executable extensions such as .php, .phtml, .php5, .php7, or .exeAffected if Executable file types are present in the upload directory
The environment is affected if the WP MLM SOFTWARE plugin version 4.0 or lower is installed and the file upload feature is accessible, regardless of whether malicious files are already present
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 uploads to safe, expected file types (images, documents) with server-side validation including magic byte verification, disallow executable extensions (.php, .exe, .phtml), and store uploads outside the web root or with .htaccess protection to prevent execution.
Fix this in Wp Mlm Unilevel
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51475 — 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-2023-51475 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