dbcve.org
Wordpress Learning Management SystemWordPress extension · Vibethemes

CVE-2024-56048

HIGH · 8.8 CVSS v3.1 Published 2024-12-18
Fix available
A fix is available. Upgrade to 1.9.9.1 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
Missing Authorization vulnerability in VibeThemes WPLMS wplms_plugin allows Accessing Functionality Not Properly Constrained by ACLs.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 versions <=1.9.9 contains a missing authorization vulnerability (CWE-862) where certain functionality is not properly constrained by Access Control Lists. This allows authenticated or unauthenticated users to access sensitive functions they should not have permission to access.

MitigationUpgrade WPLMS to the latest version where the authorization checks are properly implemented. If no patched version is available, implement additional access controls at the web server/application level to restrict access to vulnerable endpoints.

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
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
    Check for the presence of the wplms directory in wp-content/plugins/ on the WordPress installation filesystem, or query the WordPress plugins API endpoint /wp-json/wp/v2/plugins?search=wplms
    Affected if The WPLMS plugin directory exists in the WordPress plugins folder or is returned by the plugins API
  2. Determine installed WPLMS version
    Open the main plugin file (typically wp-content/plugins/wplms/init.php or wp-content/plugins/wplms/vibe-plugin.php) and locate the 'Version' header in the plugin comment block, or use wp-cli: wp plugin get wplms --field=version
    Affected if The reported version is lower than 1.9.9.1 (versions 1.9.9 and below are affected)
  3. Check for exposed AJAX endpoints lacking authorization
    Review the plugin's AJAX action handlers defined via add_action('wp_ajax_...') and add_action('wp_ajax_nopriv_...') calls in the plugin PHP files; verify that endpoints accessible to unauthenticated users (wp_ajax_nopriv_) include proper capability checks using current_user_can() or similar authorization validation before executing privileged operations
    Affected if AJAX endpoints registered with wp_ajax_nopriv_ execute sensitive operations (course management, user data access, admin actions) without calling current_user_can() or role verification first
  4. Inspect admin page access controls
    Examine PHP files handling admin menu registrations and page callbacks for proper permission verification; check that admin_init, admin_menu hooks or similar entry points verify user capabilities before rendering or processing administrative functions
    Affected if Admin functionality can be accessed or executed without verifying the user has administrator or appropriate elevated privileges

A user is affected if the WPLMS plugin version is 1.9.9 or below and sensitive endpoints or admin functions are accessible without proper capability verification.

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 version where the authorization checks are properly implemented. If no patched version is available, implement additional access controls at the web server/application level to restrict access to vulnerable endpoints.

Recommended fix High confidence

WPLMS version 1.9.9.1

  1. 1. Create a complete backup of the WordPress site (database and files) before making any changes.
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate the WPLMS plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update to version 1.9.9.1 or later.
  5. 5. Alternatively, download the fixed version 1.9.9.1 from a trusted source (VibeThemes official repository or WordPress.org) and upload it via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin version shows 1.9.9.1 or higher in the plugins list.
  7. 7. Test critical LMS functionality (course creation, student enrollment, admin access controls) to confirm the authorization fix works correctly.

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
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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