Namaste\! LmsWordPress extension · Kibokolabs
CVE-2024-50410
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Bob Namaste! LMS namaste-lms allows Stored XSS.This issue affects Namaste! LMS: from n/a through <= 2.6.4.
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 · high confidenceStored Cross-site Scripting (XSS) vulnerability in Namaste! LMS up to version 2.6.4 allows authenticated or unauthenticated attackers to inject malicious JavaScript code through user-supplied input that is not properly sanitized before being rendered in web pages. This stored payload executes whenever users view the affected content, potentially compromising sessions or stealing credentials.
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
< 2.6.4.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Namaste! LMS versionAccess the WordPress plugins admin page, find Namaste! LMS in the plugins list, and note the version number displayed. Alternatively, check the plugin header in the main plugin file (namaste.php) for the Version defined constant.Affected if The installed version is 2.6.4 or earlier, or any version below 2.6.4.1.
-
Identify user input points in the LMSReview Namaste! LMS settings and forms where users can submit content: course descriptions, lesson content, assignment submissions, user profile fields, or any public-facing text areas. Check the plugin admin panel for fields accepting user-generated text.Affected if The LMS has active user input forms or profile fields that accept freeform text without obvious sanitization controls visible.
-
Inspect HTML source of rendered user contentView the HTML source of pages displaying user-submitted content (courses, lessons, profiles). Right-click and select 'View Page Source' or use browser developer tools to examine the rendered HTML around user inputs.Affected if User-supplied text appears in the HTML without encoding (e.g., <script> tags appear literally instead of as <script> or special characters are unescaped).
-
Test for presence of XSS payload in stored dataSubmit a test string such as <script>alert('XSS')</script> or <img src=x onerror=alert(1)> into Namaste! LMS input fields (course title, lesson content, user bio). Save the data, then view the page where it is displayed.Affected if The alert dialog fires or the script executes when viewing the page containing the submitted test string, confirming the XSS is stored and reflected without sanitization.
-
Check WordPress role and capability settingsIn WordPress admin, go to Namaste! LMS settings and review which user roles (student, instructor, manager) can create or edit content. Determine if unauthricted users can submit content.Affected if Unauthenticated users or low-privilege users can submit content that gets stored and displayed to others without sanitization.
The environment is affected if Namaste! LMS version is below 2.6.4.1 AND user-supplied content can be submitted and rendered without proper HTML encoding, allowing stored XSS execution.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.6.4.1
Implement proper input validation and output encoding/escaping for all user-supplied data before rendering in HTML. Upgrade to version 2.6.5 or later if a patched release is available. Review and sanitize all form inputs and display locations within the LMS.
2.6.4.1
- 1. Back up your WordPress database and files before performing any upgrade.
- 2. Navigate to the WordPress admin dashboard.
- 3. Go to Plugins > Installed Plugins.
- 4. Find Namaste! LMS and check if an update is available.
- 5. If an update to version 2.6.4.1 or later is available, click 'Update Now'.
- 6. Alternatively, download Namaste! LMS version 2.6.4.1 from a trusted source and upload it via Plugins > Add New > Upload Plugin.
- 7. After updating, verify the plugin is running version 2.6.4.1 or later.
- 8. Test the affected functionality to confirm the XSS vulnerability is remediated.
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
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-50410 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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