dbcve.org
Tutor LmsWordPress extension · Themeum

CVE-2024-43231

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to 2.7.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Themeum Tutor LMS allows Stored XSS.This issue affects Tutor LMS: from n/a through 2.7.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

Stored XSS vulnerability in Themeum Tutor LMS allows attackers to inject malicious scripts through unsanitized user input that gets stored in the database and executed when other users view the affected content. The improper neutralization occurs during web page generation, enabling script execution in victim browsers.

MitigationUpdate Tutor LMS to the latest version which includes proper input sanitization and output encoding. If patching is not immediately possible, implement WAF rules to detect and block XSS payloads in input fields.

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
Tutor LmsWordPress extension
Affected:< 2.7.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Tutor LMS version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins > Themeum Tutor LMS, or check the version in the plugin header files via FTP/File Manager at wp-content/plugins/tutor/ directory
    Affected if The displayed version number is lower than 2.7.4 (e.g., 2.7.3, 2.7.0, 2.6.x, etc.)
  2. Identify user input endpoints in Tutor LMS
    Review the Tutor LMS plugin for front-end forms where users can submit content (e.g., quiz answers, course reviews, Q&A sections, assignment submissions, profile fields)
    Affected if User input forms exist and accept text submissions that get stored in the database and displayed to other users
  3. Inspect database for suspicious stored scripts
    Query the WordPress database tables (especially tutor tables like wp_tutor_quiz_answers, wp_tutor_reviews, wp_tutor_q_and_a, or wp_comments if course comments are enabled) for common XSS patterns like <script>, javascript:, onload=, onerror=, img src=javascript
    Affected if Any records contain HTML script tags or JavaScript event handlers that were not intentionally authored by administrators

You are affected if Tutor LMS version is below 2.7.4 AND user-submitted content is stored and displayed within the LMS without sanitization.

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.7.4 or later
Fixed in 2.7.4
Interim mitigation

Update Tutor LMS to the latest version which includes proper input sanitization and output encoding. If patching is not immediately possible, implement WAF rules to detect and block XSS payloads in input fields.

Recommended fix Moderate confidence

Tutor LMS 2.7.4

  1. Backup your WordPress database and files before proceeding with any updates
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Find Tutor LMS in the plugin list and click 'Update now' or manually upload version 2.7.4
  4. After updating, verify the plugin version shows 2.7.4 in the plugins list
  5. Test critical Tutor LMS functionality (course creation, enrollment, quiz submissions) to ensure the update didn't break existing features
  6. Clear any server-side or CDN caches if applicable
  7. Review the site for any stored XSS indicators that may have been injected prior to the patch
Caveat No breaking changes reported in the version change; standard plugin update compatibility expected

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

Fix this in Tutor Lms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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