dbcve.org
Wordpress Learning Management SystemWordPress extension · Vibethemes

CVE-2024-56042

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-31
Fix available
A fix is available. Upgrade to 1.9.9.5.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in VibeThemes WPLMS wplms_plugin allows SQL Injection.This issue affects WPLMS: from n/a through < 1.9.9.5.3.

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 confidence

SQL Injection vulnerability in WPLMS plugin allows remote attackers to inject malicious SQL commands through unsanitized input parameters, potentially enabling complete database compromise including extraction of sensitive user data, credentials, and course content.

MitigationUpdate WPLMS plugin to version 1.9.9.5.3 or later to obtain the vendor patch. If immediate updating is not feasible, disable the plugin or implement WAF rules to block SQL injection attack patterns.

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.3

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

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

  1. Confirm WPLMS plugin is installed
    In WordPress admin, navigate to Plugins > Installed Plugins and look for 'WPLMS' or 'Vibethemes Wordpress Learning Management System'. Alternatively, check the wp-content/plugins directory for a folder named 'wplms' or similar.
    Affected if The WPLMS plugin is found and active on the WordPress site
  2. Identify installed WPLMS version
    In WordPress admin, go to Plugins > Installed Plugins > WPLMS and read the version number displayed. Alternatively, check the main plugin PHP file (usually wplms.php or index.php in the wplms folder) for a 'Version' comment or constant.
    Affected if The installed version is lower than 1.9.9.5.3 (for example, 1.9.9.5.2, 1.9.5, etc.)
  3. Verify plugin handles user input
    Review the site to identify where the plugin accepts user data: course search, user registration, course enrollment, assignment submission, quiz answers, or any forms built with WPLMS. Check if the front-end is publicly accessible.
    Affected if The plugin is active and exposes any input-handling features to users (logged-in or public)
  4. Inspect application logs for SQL injection patterns
    Check WordPress debug logs (wp-content/debug.log if enabled), server access logs (Apache/Nginx), and any WAF/firewall logs for suspicious patterns like UNION SELECT, OR 1=1, single quotes appended to parameters, or other SQL syntax in URLs and POST bodies.
    Affected if Recent or historical logs contain SQL injection attempt patterns targeting the WPLMS installation

A site is affected if it runs any version of WPLMS lower than 1.9.9.5.3 and has the plugin active with input-handling features accessible to users.

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.3 or later
Fixed in 1.9.9.5.3
Interim mitigation

Update WPLMS plugin to version 1.9.9.5.3 or later to obtain the vendor patch. If immediate updating is not feasible, disable the plugin or implement WAF rules to block SQL injection attack patterns.

Recommended fix Moderate confidence

WPLMS version 1.9.9.5.3 or later

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the WPLMS plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to the latest version.
  5. 5. Alternatively, download the latest version from WordPress.org or your VibeThemes account and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. Verify the plugin version is 1.9.9.5.3 or higher after updating.
  7. 7. Test critical LMS functionality (course enrollment, student progress, quiz submissions) to ensure the update does not break existing functionality.
Caveat Review plugin changelog for any backward-incompatible changes before upgrading in production environments

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
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-56042 — 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-56042 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