CVE-2024-1751
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 · uneditedThe Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to time-based SQL Injection via the question_id parameter in all versions up to, and including, 2.6.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber/student access or higher, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
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 confidenceThe Tutor LMS WordPress plugin versions up to 2.6.1 contain a time-based SQL injection vulnerability in the question_id parameter. Authenticated users with subscriber/student access can inject malicious SQL queries due to insufficient escaping and lack of prepared statements in the existing SQL query, allowing extraction of sensitive database information.
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< 2.6.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Tutor LMS is installed and activeLog into WordPress admin and navigate to Plugins > Installed Plugins, or use WP-CLI: wp plugin list --status=active --filter=name=tutorAffected if Tutor LMS plugin is installed and active on the WordPress site
-
Check installed Tutor LMS versionIn WordPress admin, go to Plugins > Installed Plugins and find Tutor LMS to view the version number, or check the plugin header in wp-content/plugins/tutor/ VERSION file or main plugin PHP fileAffected if The installed version is 2.6.1 or lower (any version below 2.6.2)
-
Confirm low-privilege user roles can access quiz question functionalityReview WordPress user roles and capabilities. Check if subscriber or student role exists and has access to quiz/assignment features. Navigate to Users > All Users in WP admin to see existing roles, or inspect the tutor plugin capability settingsAffected if Subscriber or student roles exist and are permitted to access quiz question review features where question_id parameter is used
If Tutor LMS version is below 2.6.2 AND low-privilege authenticated users (subscriber/student) can access the question_id parameter in quiz functionality, the site is vulnerable to SQL injection.
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.2
Update Tutor LMS to version 2.6.2 or later. If immediate update is not possible, implement input validation on the question_id parameter and refactor vulnerable queries to use WordPress $wpdb->prepare() prepared statements.
Tutor LMS 2.6.2
- 1. Back up your WordPress database and files before making any changes
- 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
- 3. Find Tutor LMS in the plugin list
- 4. If an update is available, click 'Update Now' to upgrade to version 2.6.2 or later
- 5. Alternatively, download Tutor LMS version 2.6.2 or newer from the WordPress plugin repository
- 6. Upload the new version via Plugins > Add New > Upload Plugin
- 7. Verify the plugin version after update to confirm 2.6.2 or higher is installed
- 8. Test that the course and question functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1751 — 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-1751 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