dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-6184

HIGH · 8.8 CVSS v3.1 Published 2025-08-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The Tutor LMS Pro – eLearning and online course solution plugin for WordPress is vulnerable to time-based SQL Injection via the ‘order’ parameter used in the get_submitted_assignments() function in all versions up to, and including, 3.7.0 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 Tutor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Only the Pro version is affected.

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 confidence

The Tutor LMS Pro plugin for WordPress contains a time-based SQL Injection vulnerability in the get_submitted_assignments() function via the 'order' parameter. The vulnerability stems from insufficient escaping of user-supplied input and lack of prepared statement usage in the SQL query, allowing authenticated attackers with Tutor-level access to inject malicious SQL queries and extract sensitive database information.

MitigationUpdate Tutor LMS Pro to version 3.7.1 or later to receive the official patch. If immediate update is not possible, implement input validation on the 'order' parameter and refactor the vulnerable function to use prepared statements.

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
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 checks

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

  1. Confirm Tutor LMS Pro is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Tutor LMS Pro' or check the plugin files in /wp-content/plugins/tutor-pro/ for the main plugin file
    Affected if Tutor LMS Pro plugin is not installed or not active
  2. Identify the installed version
    In WordPress admin_plugins list, the version is shown next to the plugin name, or open the main plugin file (e.g., tutor-pro.php) and look for the 'Version' header in the plugin comments
    Affected if Version is 3.7.0 or lower
  3. Verify assignment feature is in use
    Check if the site has any courses with assignments enabled. Navigate to Tutor LMS > Assignments or inspect the database table wp_posts for posts of type 'tutor_assignment'
    Affected if Assignments exist and the get_submitted_assignments() function is accessible
  4. Confirm Tutor-level user access exists
    Check WordPress users list for any user role that includes Tutor capabilities (Tutor Instructor, Tutor Administrator, etc.) or inspect user_meta for tutor_capability
    Affected if At least one user with Tutor-level access exists on the site

You are affected if Tutor LMS Pro version 3.7.0 or lower is installed AND assignments are enabled AND users with Tutor-level access exist on the site.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Tutor LMS Pro to version 3.7.1 or later to receive the official patch. If immediate update is not possible, implement input validation on the 'order' parameter and refactor the vulnerable function to use prepared statements.

Recommended fix Moderate confidence

Latest version greater than 3.7.0 (check tutorlms.com for the current stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Tutor LMS Pro' in the plugin list
  4. Check if an update is available for the Tutor LMS Pro plugin
  5. If an update is available, click 'Update Now' to install the latest version
  6. If no update appears, manually download the latest version from tutorlms.com or your purchase source and upload it via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin version is greater than 3.7.0
  8. Test that the assignment submission functionality works correctly
Caveat Review plugin changelog for any breaking changes between your current version and the new version before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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