dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-58993

HIGH · 7.6 CVSS v3.1 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Themeum Tutor LMS tutor allows SQL Injection.This issue affects Tutor LMS: from n/a through <= 3.7.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 · moderate confidence

SQL Injection vulnerability in Themeum Tutor LMS plugin allows attackers to inject malicious SQL commands through unsanitized user input in database queries, potentially enabling unauthorized data access, modification, or exfiltration.

MitigationApply input sanitization and use parameterized queries/prepared statements for all database interactions in the affected plugin code paths.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L

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. Confirm Themeum Tutor LMS is installed
    Check your WordPress plugins directory or WordPress admin panel for the Tutor LMS plugin. If using command line, search for 'tutor' in wp-content/plugins/
    Affected if The plugin is present in the WordPress installation
  2. Identify installed Tutor LMS version
    Check the plugin header in main plugin file (usually wp-content/plugins/tutor/tutor.php) for 'Version:' tag, or query via WordPress admin > Plugins > Tutor LMS
    Affected if Version cannot be determined or is below the latest patched version
  3. Verify database query handling
    Examine plugin PHP files that handle database queries, particularly looking for direct $wpdb->query(), $wpdb->get_results(), or similar calls that concatenate user input into SQL strings without using $wpdb->prepare()
    Affected if User-supplied input (from $_GET, $_POST, $_REQUEST) is used directly in SQL queries without prepared statements or escaping functions
  4. Check input sanitization on affected code paths
    Review files in the tutor/includes or tutor/classes directories for database interactions. Look for $_POST, $_GET, or $_REQUEST variables passed to query functions without sanitization functions like sanitize_text_field()
    Affected if User parameters flow into database queries without sanitization or parameterization

A user is affected if the Tutor LMS plugin is installed and its codebase contains direct user input in SQL queries without using prepared statements or proper escaping functions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply input sanitization and use parameterized queries/prepared statements for all database interactions in the affected plugin code paths.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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