dbcve.org
Wordpress Learning Management SystemWordPress extension · Vibethemes

CVE-2024-56044

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-31
Fix available
A fix is available. Upgrade to 1.9.9.1 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
Authentication Bypass Using an Alternate Path or Channel vulnerability in VibeThemes WPLMS wplms_plugin allows Authentication Bypass.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 confidence

The WPLMS WordPress plugin (a learning management system) versions up to 1.9.9 contain an authentication bypass vulnerability allowing attackers to circumvent normal authentication mechanisms through an alternate path or channel. The high CVSS score (9.8) indicates this is exploitable remotely without prior authentication and grants unauthorized access to protected functionality.

MitigationUpgrade WPLMS to the latest patched version if available. If no patch exists, disable the plugin or implement additional authentication safeguards such as Web Application Firewall rules,强制多因素认证, and temporary access restrictions while awaiting an official fix.

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

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
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'WPLMS' or 'Vibethemes Wordpress Learning Management System' in the plugin list.
    Affected if WPLMS plugin appears in the installed plugins list
  2. Identify installed WPLMS version
    In the Plugins list, locate the WPLMS entry and note the version number displayed beneath the plugin name. Alternatively, check the plugin header in the main plugin file (typically wp-content/plugins/wplms/init.php or wplms.php).
    Affected if Version displayed is 1.9.9 or lower, or version cannot be determined (plugin may be outdated/unmaintained)
  3. Compare against vulnerable version range
    Compare your installed version to the affected range: versions less than 1.9.9.1 are vulnerable. Check if your version shows 1.9.9, 1.9.8, or any version below 1.9.9.1.
    Affected if Installed version is less than 1.9.9.1 (for example: 1.9.9, 1.9.8, 1.9.7, etc.)
  4. Verify authentication is functioning
    Test login functionality with valid credentials on the WPLMS login page or wp-login.php. Attempt to access protected course content or admin areas without credentials to confirm whether authentication is being enforced.
    Affected if Authentication can be bypassed - anonymous or unauthenticated access to protected resources is possible

You are affected if WPLMS plugin is installed and the version is below 1.9.9.1, especially if the authentication bypass allows unauthenticated access to protected content or admin functions.

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.1 or later
Fixed in 1.9.9.1
Interim mitigation

Upgrade WPLMS to the latest patched version if available. If no patch exists, disable the plugin or implement additional authentication safeguards such as Web Application Firewall rules,强制多因素认证, and temporary access restrictions while awaiting an official fix.

Recommended fix Moderate confidence

1.9.9.1

  1. Back up your WordPress database and files
  2. Log in to WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Find WPLMS plugin in the list
  5. Check if an update to version 1.9.9.1 is available
  6. If update available, click 'Update Now' to install version 1.9.9.1
  7. If no automatic update appears, manually upload the WPLMS 1.9.9.1 plugin zip file via Plugins > Add New > Upload Plugin
  8. Verify the plugin is running version 1.9.9.1 after updating

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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