dbcve.org
Wordpress Learning Management SystemWordPress extension · Vibethemes

CVE-2024-56051

HIGH · 8.8 CVSS v3.1 Published 2024-12-18
Fix available
A fix is available. Upgrade to 1.9.9.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Improper Control of Generation of Code ('Code Injection') vulnerability in VibeThemes WPLMS wplms_plugin allows Code Injection.This issue affects WPLMS: from n/a through < 1.9.9.5.

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 confidence

This is a code injection vulnerability in the WPLMS WordPress plugin from VibeThemes. The vulnerability allows remote attackers to inject malicious code through improper input handling in the plugin, likely due to insufficient sanitization of user-supplied data before it is processed or executed server-side.

MitigationUpdate WPLMS plugin to version 1.9.9.5 or later to receive the security patch. If immediate update is not possible, restrict access to the plugin's admin interfaces and monitor for suspicious activity.

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
Affected:< 1.9.9.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WPLMS plugin installation
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WPLMS' or 'Vibethemes Wordpress Learning Management System' in the plugin list. Alternatively, check the wp-content/plugins/ directory for a folder named 'wplms' or similar.
    Affected if WPLMS plugin is found in the WordPress installation
  2. Identify installed WPLMS version
    In WordPress admin under Plugins > Installed Plugins, click on the WPLMS plugin to view its details, which typically displays the version number. Alternatively, open the main plugin file (usually wplms.php or similar in the plugin directory and read the version header comment.
    Affected if Version displayed is below 1.9.9.5
  3. Verify plugin is active
    In WordPress admin under Plugins > Installed Plugins, confirm the WPLMS plugin status shows as 'Active'. Check the site frontend to verify the plugin functionality is operational.
    Affected if Plugin is active and serving pages
  4. Assess exposure to user input handling
    Review the WPLMS plugin settings and enabled modules. Identify any features that process or display user-submitted data such as course submissions, assignments, user profiles, or frontend forms. Check if these features are accessible to unauthenticated or lower-privileged users.
    Affected if Features handling user input are enabled and publicly accessible

If the WPLMS plugin is installed, active, and running version 1.9.9.5 or lower, the environment is vulnerable to CVE-2024-56051.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.9.9.5 or later
Fixed in 1.9.9.5
Interim mitigation

Update WPLMS plugin to version 1.9.9.5 or later to receive the security patch. If immediate update is not possible, restrict access to the plugin's admin interfaces and monitor for suspicious activity.

Recommended fix High confidence

1.9.9.5 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WPLMS' (WordPress Learning Management System) in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 1.9.9.5 or later
  5. Verify the update completed successfully
  6. Test critical functionality (course creation, user enrollment, quiz submissions) to ensure the plugin works correctly after update
Caveat Review plugin changelog and test in staging before production deployment

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-56051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-56051 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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