dbcve.org
Wordpress Learning Management SystemWordPress extension · Vibethemes

CVE-2024-56047

HIGH · 8.8 CVSS v3.1 Published 2024-12-18
Fix available
A fix is available. Upgrade to 1.9.9.5.3 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 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 · moderate confidence

SQL injection vulnerability in WPLMS plugin allows attackers to inject malicious SQL commands through unsanitized user input. This could enable unauthorized database access, data exfiltration, or authentication bypass.

MitigationUpgrade WPLMS to version 1.9.9.5.3 or later which contains the fix for this SQL injection vulnerability.

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
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. Verify WPLMS plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WPLMS' or 'Vibethemes Wordpress Learning Management System' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wplms' or similar.
    Affected if WPLMS plugin is not found in the WordPress installation
  2. Check the installed WPLMS version
    In WordPress admin, go to Plugins > Installed Plugins and locate WPLMS. The version number is displayed below the plugin name. Alternatively, check the main plugin file (typically /wp-content/plugins/wplms/init.php or /wp-content/plugins/wplms/wplms.php) for a version constant or header.
  3. Compare version against affected range
    Compare the installed version number to the affected range: versions below 1.9.9.5.3 are vulnerable. For example, 1.9.9.5.2 or 1.9.9.4 are affected; 1.9.9.5.3 and later are not.
    Affected if Installed version is below 1.9.9.5.3 (e.g., 1.9.9.5, 1.9.9.4, 1.9.8, etc.)

If WPLMS is installed and the version is below 1.9.9.5.3, the environment is affected by this SQL injection vulnerability.

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

Upgrade WPLMS to version 1.9.9.5.3 or later which contains the fix for this SQL injection vulnerability.

Recommended fix High confidence

1.9.9.5.3

  1. 1. Back up your WordPress site and database before performing any updates.
  2. 2. Navigate to the WordPress admin dashboard.
  3. 3. Go to Plugins > Installed Plugins.
  4. 4. Locate the WPLMS plugin in the list.
  5. 5. If an update is available, click 'Update Now' to upgrade to version 1.9.9.5.3 or later.
  6. 6. Alternatively, download the fixed version (1.9.9.5.3 or higher) from VibeThemes and manually upload it via Plugins > Add New > Upload Plugin.
  7. 7. After updating, verify the plugin version shows 1.9.9.5.3 or higher.
  8. 8. Test critical functionality (course enrollment, user management, quiz submissions) to ensure the update did not break existing features.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wordpress Learning Management System Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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