dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-22332

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Unauthenticated SQL Injection in Tutor LMS Pro <= 3.9.6 versions.

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

An unauthenticated SQL injection vulnerability exists in Tutor LMS Pro plugin for WordPress versions 3.9.6 and below. Attackers can exploit vulnerable parameters without authentication to inject and execute arbitrary SQL queries, potentially leading to data exfiltration or complete database compromise.

MitigationUpgrade Tutor LMS Pro to a version newer than 3.9.6; as an interim control, deploy a WAF rule to detect and block SQL injection payloads targeting the application.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Tutor LMS Pro is installed
    Check for the Tutor LMS plugin directory at wp-content/plugins/tutor or access the WordPress admin under Plugins > Installed Plugins to confirm Tutor LMS Pro is present
    Affected if Tutor LMS Pro plugin is not installed on the WordPress site
  2. Check installed version number
    Access the WordPress admin dashboard, navigate to Plugins > Instored Plugins, and locate the Tutor LMS Pro entry to view the installed version number. Alternatively, inspect the main plugin file (e.g., tutor-lms.php) in wp-content/plugins/tutor for the 'Version' header comment
    Affected if The installed version is 3.9.6 or any version lower than 3.9.6
  3. Confirm plugin is active
    In the WordPress admin under Plugins > Installed Plugins, verify that Tutor LMS Pro is activated. An inactive plugin may still be exploitable if the files remain on the server
    Affected if Tutor LMS Pro is activated and accessible to unauthenticated users
  4. Identify exposed parameters
    Review publicly accessible URLs on the site, particularly those handling course, lesson, quiz, assignment, or user enrollment data. These are typical attack vectors for SQL injection in LMS plugins
    Affected if Publicly accessible parameters exist that accept user input without authentication and interact with the database

The environment is affected if Tutor LMS Pro version 3.9.6 or below is installed and active, with unauthenticated endpoints handling database queries exposed to the internet.

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

Upgrade Tutor LMS Pro to a version newer than 3.9.6; as an interim control, deploy a WAF rule to detect and block SQL injection payloads targeting the application.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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