Tutor LmsWordPress extension · Themeum
CVE-2023-25990
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 Special Elements used in an SQL Command ('SQL Injection') vulnerability in Themeum Tutor LMS allows SQL Injection.This issue affects Tutor LMS: from n/a through 2.1.10.
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 confidenceSQL injection vulnerability in Themeum Tutor LMS WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user input in SQL queries. This could enable unauthorized database access, data exfiltration, or modification.
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
<= 2.1.10CVSS 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.
-
Confirm Tutor LMS plugin installationIn WordPress admin, go to Plugins > Installed Plugins and locate 'Themeum Tutor LMS' or check the plugin files for version information in the main plugin PHP file headerAffected if Plugin is not installed or not present in the system
-
Identify installed Tutor LMS versionCheck the plugin version number in the WordPress plugin list or in the plugin's main PHP file (typically tutor.php) in the plugin directoryAffected if Version number is 2.1.10 or lower (any version <= 2.1.10)
-
Verify vulnerable SQL query execution is possibleThe vulnerability exists in SQL queries that use unsanitized user input. Identify if any Tutor LMS features that accept user input (such as search, filtering, or form submissions) are in active useAffected if The plugin processes user input through SQL queries without proper prepared statements or input sanitization
-
Review access to affected query endpointsDetermine if unauthenticated or low-privilege users can submit input to the affected plugin features. Check WordPress user role permissions for Tutor LMS functionalityAffected if Users with limited privileges (subscriber, student, or unauthenticated visitors) can trigger the vulnerable SQL queries
System is affected if Tutor LMS version is 2.1.10 or lower and user input can reach the vulnerable SQL query code paths.
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.
From vendor dataUpdate Tutor LMS to the latest patched version beyond 2.1.10. If no update is available, audit the codebase for vulnerable SQL query construction and implement prepared statements/parameterized queries with proper input sanitization.
Fix this in Tutor Lms
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25990 — 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-2023-25990 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