dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-40766

HIGH · 8.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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
Subscriber SQL Injection in MasterStudy LMS <= 3.7.25 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

SQL injection vulnerability in MasterStudy LMS WordPress plugin allows authenticated users with subscriber-level privileges to execute arbitrary SQL queries through unsanitized input in versions 3.7.25 and below.

MitigationUpdate MasterStudy LMS to a version newer than 3.7.25, or apply vendor-supplied security patch if available. Verify WordPress core and other plugin compatibility post-update.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 MasterStudy LMS is installed
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate MasterStudy LMS in the list. Confirm the plugin is active.
    Affected if MasterStudy LMS plugin is present and active in WordPress
  2. Check installed version number
    In the Plugins list, find MasterStudy LMS and view the version number displayed beneath the plugin name. Compare this to 3.7.25.
    Affected if Installed version is 3.7.25 or lower
  3. Identify subscriber-level user accounts
    Navigate to Users > All Users in WordPress admin. Review the roles column to determine if any users have the Subscriber role assigned.
    Affected if At least one user with Subscriber role exists in WordPress
  4. Confirm user registration is enabled
    Go to Settings > General in WordPress admin. Check if Membership option is enabled allowing anyone to register, and verify the default New User Role is set to Subscriber.
    Affected if User registration is enabled with Subscriber as the default role

Your environment is affected if MasterStudy LMS version 3.7.25 or lower is installed and active with subscriber-level user accounts present.

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

Update MasterStudy LMS to a version newer than 3.7.25, or apply vendor-supplied security patch if available. Verify WordPress core and other plugin compatibility post-update.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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