Wordpress Learning Management SystemWordPress extension · Vibethemes
CVE-2024-56054
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 · high confidenceThe WPLMS WordPress plugin before version 1.9.5.2 contains an unrestricted file upload vulnerability that allows authenticated attackers to upload arbitrary files, including malicious PHP web shells. This enables complete remote code execution on the affected WordPress 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
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.
-
Verify WPLMS plugin versionIn WordPress admin, go to Plugins > Installed Plugins > WPLMS and check the version number displayed. Alternatively, inspect the plugin header in /wp-content/plugins/wplms/includes/version.php or the main plugin file.Affected if The installed version is lower than 1.9.9.5.2
-
Confirm file upload feature is accessibleCheck if the course attachment or assignment upload functionality is enabled on the site. Navigate to a course with upload-enabled assignments or check the WPLMS settings under LMS Settings > Course Settings > Enable Attachments.Affected if File upload functionality is enabled and accessible to authenticated users (especially student-level users)
-
Inspect upload directories for suspicious filesExamine the /wp-content/uploads/ directory (or custom upload path configured in WordPress) for recently added .php files, .php.txt files, or other web shell variants. Use file system commands to list files modified within recent days.Affected if Unexpected PHP files exist in upload directories, especially in course attachment folders or locations not explicitly created by administrators
-
Review user roles with upload permissionsIn WordPress admin, go to Users > All Users and check which user roles (especially Student or Instructor) have capability to upload files. Verify under WPLMS > Settings that course instructors or students are granted upload permissions.Affected if Users with low-privilege roles (Subscriber, Student) have upload capabilities enabled in WPLMS settings
You are affected if WPLMS version is below 1.9.9.5.2 AND file upload functionality is enabled for authenticated users on your site.
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 to version 1.9.9.5.2 or later. Until patched, disable file upload functionality or restrict upload capabilities to trusted users only.
WPLMS plugin version 1.9.9.5.2 or later
- Backup your WordPress site and database before making any changes
- Navigate to WordPress admin dashboard > Plugins
- Locate the WPLMS plugin in the installed plugins list
- Check the current version of the WPLMS plugin to confirm it is below 1.9.9.5.2
- Update the WPLMS plugin to the latest available version (1.9.9.5.2 or later)
- Verify the update was successful by checking the plugin version after update
- Test critical LMS functionality (course creation, student enrollment, assignment uploads) to ensure the update did not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wordpress Learning Management System
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56054 — 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-56054 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