dbcve.org
Namaste\! LmsWordPress extension · Kibokolabs

CVE-2024-50408

HIGH · 8.8 CVSS v3.1 Published 2024-10-28
Fix available
A fix is available. Upgrade to 2.6.4 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
Deserialization of Untrusted Data vulnerability in Bob Namaste! LMS namaste-lms allows Object Injection.This issue affects Namaste! LMS: from n/a through <= 2.6.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

A deserialization of untrusted data vulnerability in Namaste! LMS (version <= 2.6.3) allows PHP object injection, potentially enabling remote code execution if vulnerable classes are present in the application context.

MitigationUpdate to the latest patched version of Namaste! LMS immediately. If no patched version is available, disable the plugin or restrict access to the vulnerable endpoint via web server configuration.

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
Namaste\! LmsWordPress extension
Affected:< 2.6.4

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 Namaste! LMS plugin is installed
    Locate the Namaste! LMS plugin files in your WordPress wp-content/plugins directory or check via WordPress admin plugins list
    Affected if The plugin is present in the environment
  2. Determine installed plugin version
    Check the plugin header in namaste-lms.php or the version defined in the plugin's main file, typically found in /wp-content/plugins/namaste-lms/
    Affected if Version is lower than 2.6.4 (e.g., 2.6.3, 2.6.0, etc.)
  3. Identify PHP files using unserialize() on input
    Search plugin PHP files for unserialize() calls that process $_GET, $_POST, $_REQUEST, or other user-supplied data without validation
    Affected if Code exists that calls unserialize() on untrusted (non-validated) input
  4. Check access to vulnerable endpoint
    Review web server logs and plugin routing to identify endpoints that handle serialized data submissions
    Affected if An endpoint accepting user input is wired to the vulnerable unserialize() call
  5. Review PHP error logs for injection attempts
    Examine PHP error logs for class instantiation errors or unserialize warnings that may indicate exploitation attempts
    Affected if Log entries show unserialize activity or PHP object injection errors

If Namaste! LMS version is below 2.6.4 AND your installation contains code paths that pass untrusted input to PHP's unserialize() function, your environment is affected by this CVE.

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 2.6.4 or later
Fixed in 2.6.4
Interim mitigation

Update to the latest patched version of Namaste! LMS immediately. If no patched version is available, disable the plugin or restrict access to the vulnerable endpoint via web server configuration.

Recommended fix High confidence

Namaste! LMS version 2.6.4

  1. Backup your WordPress database and files before proceeding
  2. Ensure you have a recent backup of your Namaste! LMS installation
  3. Update Namaste! LMS plugin through WordPress admin dashboard (Plugins > Namaste! LMS > Update Now), or upload version 2.6.4 manually via FTP/sFTP if automatic update is unavailable
  4. Verify the update was successful by checking the plugin version in WordPress admin
  5. Test critical LMS functionality (course enrollment, lesson completion, quiz submissions) to confirm the upgrade did not break existing features
  6. Review your site's error logs for any issues following the upgrade
Caveat No specific breaking changes documented in the provided material; standard WordPress plugin upgrade risks apply (test in staging first if possible)

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

Fix this in Namaste\! Lms 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-50408 — 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-50408 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