Wordpress Learning Management SystemWordPress extension · Vibethemes
CVE-2024-56043
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 · uneditedIncorrect Privilege Assignment vulnerability in VibeThemes WPLMS wplms_plugin allows Privilege Escalation.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 contains an Incorrect Privilege Assignment vulnerability that allows authenticated users to escalate their privileges beyond what should be permitted for their assigned role. This privilege escalation flaw enables lower-privileged users (such as subscribers or students) to gain administrative-level access to the Learning Management 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.
-
Verify WPLMS plugin is installedNavigate to WordPress admin dashboard > Plugins. Look for 'WPLMS' or 'Vibethemes Wordpress Learning Management System' in the installed plugins list.Affected if WPLMS plugin is not found in the plugins list, then the environment is not affected by this CVE.
-
Identify installed WPLMS versionIn the Plugins list, locate the WPLMS plugin entry. The version number is displayed beneath the plugin name. Alternatively, open /wp-content/plugins/wplms/readme.txt and check the 'Stable tag' line, or inspect the main plugin PHP file header for 'Version' information.Affected if The version displayed is lower than 1.9.9.1 (for example, 1.9.9, 1.9.8, etc.).
-
Confirm user role assignment settings are accessibleCheck if the plugin allows lower-privileged users to modify or assign roles. Look for WPLMS-specific settings under Users > WPLMS Users, or in the plugin settings panel under LMS > Course Settings > User Roles. Verify whether subscribers, students, or other low-privileged roles have the ability to change user roles or permissions.Affected if Subscribers, students, or other non-administrative users have role modification capabilities enabled in the WPLMS settings.
-
Review user capability assignmentsAccess the WordPress database via phpMyAdmin or WP-CLI. Query the wp_options table for option_name values containing 'wplms' or 'capabilities'. Also check if any custom role definitions exist in the wp_usermeta table that grant administrative-level capabilities to lower roles.Affected if User metadata shows that subscribers or students have been granted administrative capabilities or have their role set to administrator.
Your environment is affected if the WPLMS plugin version is below 1.9.9.1 AND lower-privileged users have access to role modification features or have been granted elevated capabilities.
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
Upgrade WPLMS to the latest patched version immediately. If no patch is available, disable the plugin until a fix is released, or implement strict access controls at the web application firewall level to restrict user role modifications.
WPLMS version 1.9.9.1
- Backup your WordPress site database and files
- Update the WPLMS plugin to version 1.9.9.1 or later through WordPress admin dashboard (Plugins > Updates) or via FTP/SFTP
- Verify the updated plugin version is 1.9.9.1 or higher in the installed plugins list
- Test that user role permissions work correctly post-update
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 / 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-2024-56043 — 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-56043 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