Wordpress Learning Management SystemWordPress extension · Vibethemes
CVE-2024-56057
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.5.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 confidenceUnrestricted file upload vulnerability in the WPLMS WordPress plugin allows authenticated attackers to upload malicious PHP files (web shells) to the server, potentially achieving remote code execution.
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.5.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 WPLMS plugin is installedCheck the WordPress plugins directory for the WPLMS plugin folder, or run 'wp plugin list --status=active' via WP-CLI to list active pluginsAffected if WPLMS appears in the list of installed or active plugins
-
Check installed WPLMS versionNavigate to WordPress Admin > Plugins > Installed Plugins and locate WPLMS, or inspect the main plugin file header for the Version constant, or run 'wp plugin get wplms --field=version' via WP-CLIAffected if The version number displayed is lower than 1.9.9.5.2
-
Verify file upload functionality is accessibleCheck if the course attachment, assignment upload, or any file upload endpoints are accessible on the frontend of the site (typically under /wp-content/uploads/ or course-related AJAX endpoints)Affected if File upload forms or endpoints are publicly accessible without admin authentication
-
Confirm upload directory is within webrootInspect the WordPress media library upload path (typically /wp-content/uploads/) and verify if uploaded files are stored in a directory accessible via HTTPAffected if Uploaded files can be accessed directly via a web browser URL, enabling execution of uploaded web shells
If WPLMS is installed with a version below 1.9.9.5.2 and file upload functionality is accessible from the web, 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.
dbcve · scoped1.9.9.5.2
Update WPLMS plugin to version 1.9.9.5.2 or later to patch the vulnerability. If immediate update is not feasible, disable or restrict the file upload functionality and implement server-side file type validation.
1.9.9.5.2 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the WPLMS plugin in the list
- Check if the current version is below 1.9.9.5.2
- If update available, click 'Update Now' on the WPLMS plugin
- Alternatively, download the latest version from VibeThemes or WordPress repository
- Deactivate the old version, delete it, then upload and activate the new version
- Verify the update was successful by checking the plugin version number
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wordpress Learning Management System
Scoped from the published advisory
- Consultation2.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56057 — 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-56057 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