dbcve.org
Wordpress Learning Management SystemWordPress extension · Vibethemes

CVE-2024-56055

HIGH · 8.8 CVSS v3.1 Published 2024-12-18
Fix available
A fix is available. Upgrade to 1.9.9.5.2 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
Path Traversal: '.../...//' vulnerability in VibeThemes WPLMS wplms_plugin allows Path Traversal.This issue affects WPLMS: from n/a through < 1.9.9.5.2.

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

A path traversal vulnerability in the WPLMS WordPress plugin by VibeThemes allows attackers to access files outside the web root directory using specially crafted '.../...//' sequences in HTTP requests. This occurs due to insufficient input validation in the plugin.

MitigationUpdate WPLMS plugin to version 1.9.9.5.2 or later to patch the path traversal vulnerability. If immediate patching is not possible, restrict access to the affected plugin endpoints at the web server level.

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

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 is installed
    Check your WordPress installation for the WPLMS plugin by VibeThemes. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard and look for 'WPLMS' or 'Wordpress Learning Management System' in the plugin list.
    Affected if The WPLMS plugin appears in your installed plugins list
  2. Identify installed WPLMS version
    In the WordPress admin, go to Plugins > Installed Plugins and locate the WPLMS plugin entry. The version number is displayed beneath the plugin name.
    Affected if The displayed version number is lower than 1.9.9.5.2 (for example, 1.9.9.5, 1.9.9.4, or earlier versions)
  3. Verify vulnerable endpoint accessibility
    Test if the path traversal endpoint is accessible by sending a crafted HTTP request with '.../...//' sequences to your site. This typically targets plugin AJAX handlers or file inclusion functions. Use a tool like curl: curl -v https://your-site.com/wp-admin/admin-ajax.php?action=... (the specific action parameter depends on the plugin's implementation).
    Affected if The server returns file contents from outside the web root directory or exposes sensitive filesystem data
  4. Check for web server access restrictions
    Review your web server configuration (Apache .htaccess, Nginx config, or WAF rules) to determine if access to the WPLMS plugin directory and its AJAX endpoints is restricted. Look for rules that deny or limit access to /wp-content/plugins/wplms/ paths.
    Affected if No access restrictions are configured for the WPLMS plugin endpoints, making them directly accessible to unauthenticated users

Your environment is affected if the WPLMS plugin is installed and its version is below 1.9.9.5.2, and the vulnerable endpoint is accessible without restrictions.

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.2 or later
Fixed in 1.9.9.5.2
Interim mitigation

Update WPLMS plugin to version 1.9.9.5.2 or later to patch the path traversal vulnerability. If immediate patching is not possible, restrict access to the affected plugin endpoints at the web server level.

Recommended fix Moderate confidence

WPLMS version 1.9.9.5.2 or latest stable release

  1. 1. Backup your WordPress database and all files before proceeding with any changes
  2. 2. Verify current WPLMS version by checking wp-admin > Plugins > WPLMS or inspecting plugin header in wp-content/plugins/wplms/plugin.php
  3. 3. Navigate to wp-admin > Plugins > WordPress Updates or check VibeThemes member dashboard for latest version
  4. 4. Download WPLMS version 1.9.9.5.2 or latest stable release from VibeThemes (themeforest.net or member dashboard)
  5. 5. Deactivate the current WPLMS plugin from wp-admin > Plugins
  6. 6. Delete the existing WPLMS plugin files (backup any custom modifications to template files in wplms-templates folder first)
  7. 7. Upload and install the new WPLMS version
  8. 8. Reactivate the plugin and verify front-end and admin functionality
Caveat Custom template overrides in wplms-templates folder may require review against updated parent templates; verify child theme compatibility after upgrade

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-56055 — 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-56055 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