Wordpress Learning Management SystemWordPress extension · Vibethemes
CVE-2024-56046
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 VibeThemes WPLMS wplms_plugin allows Upload a Web Shell to a Web Server.This issue affects WPLMS: from n/a through <= 1.9.9.
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 WPLMS WordPress plugin has an unrestricted file upload vulnerability that allows attackers to upload dangerous file types (such as PHP files) directly to the web server. This can result in remote code execution via a web shell, giving attackers full control over the affected system.
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
Wordpress Learning Management SystemWordPress extension
< 1.9.9.1CVSS 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.
-
Identify WPLMS plugin versionAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate WPLMS (Vibethemes Wordpress Learning Management System) and read the version number from the plugin details. Alternatively, check the main plugin file header in wp-content/plugins/wplms or similar directory for the 'Version' field.Affected if The displayed version is below 1.9.9.1 (for example, 1.9.9.0, 1.9.8, etc.)
-
Locate file upload functionalityIdentify the upload handler script used by WPLMS. Common paths include wp-content/plugins/wplms/includes/upload.php, wp-content/plugins/wplms/assets/uploads/, or similar directories containing PHP upload handlers. Search for files with 'upload' in the name within the plugin directory.Affected if An upload handler PHP file exists and is accessible via web request without authentication restrictions.
-
Inspect upload validation logicOpen the identified upload handler file and examine the file validation section. Look for code that checks file type, extension, or content before saving the file. Search for functions like wp_check_filetype, mime_content_type, or custom validation logic.Affected if The code lacks validation (no extension whitelist, no MIME type check, no magic byte verification) or contains only client-side checks that can be bypassed.
-
Verify uploaded files are executableCheck the upload directory configuration. Determine where uploaded files are stored (wp-content/uploads/ or plugin-specific directories) and whether .htaccess or server configuration prevents PHP execution in that directory.Affected if Uploaded files are stored within the webroot with .php extension and no server-side protection prevents direct execution via HTTP.
-
Test upload capability (if safe to do so)Using an authorized test account with upload privileges, attempt to upload a benign file with .php extension (for example, a file containing only <?php echo 'test'; ?> ) to the WPLMS upload endpoint and then access the file URL via browser.Affected if The .php file is successfully uploaded and accessible via HTTP, allowing potential remote code execution.
Your environment is affected if WPLMS version is below 1.9.9.1 AND the plugin's upload functionality permits PHP files to be stored in an accessible web directory without proper validation.
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.
dbcve · scoped1.9.9.1
Implement strict file type validation on upload endpoints, including extension allowlist, MIME type verification, and file content inspection. Store uploaded files outside the web root or use .htaccess/nginx directives to prevent execution of uploaded files.
WPLMS version 1.9.9.1 or later
- Backup your WordPress database and files before proceeding
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the WPLMS plugin in the list
- Click Update Now on the WPLMS plugin, or go to Plugins > Add New > Upload and install version 1.9.9.1 or later
- Verify the plugin version after update to confirm 1.9.9.1 or newer is installed
- Clear any caching mechanisms if enabled
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wordpress Learning Management System
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56046 — 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-56046 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