SQL InjectionWeakness · CWE-89

CVE-2026-4817

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-17

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

71/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

The MasterStudy LMS WordPress Plugin for Online Courses and Education plugin for WordPress is vulnerable to Time-based Blind SQL Injection via the 'order' and 'orderby' parameters in the /lms/stm-lms/order/items REST API endpoint in versions up to and including 3.7.25. This is due to insufficient input sanitization combined with a design flaw in the custom Query builder class that allows unquoted SQL injection in ORDER BY clauses. When the Query builder detects parentheses in the sort_by parameter, it treats the value as a SQL function and directly concatenates it into the ORDER BY clause without any quoting. While esc_sql() is applied to escape quotes and backslashes, this cannot prevent ORDER BY injection when the values themselves are not wrapped in quotes in the resulting SQL statement. This makes it possible for authenticated attackers, with subscriber-level access and above, to append arbitrary SQL queries via the ORDER BY clause to extract sensitive information from the database including user credentials, session tokens, and other confidential data through time-based blind SQL injection techniques.

Technical summary

dbcve analysis · high confidence

The MasterStudy LMS WordPress plugin contains a time-based blind SQL injection vulnerability in the /lms/stm-lms/order/items REST API endpoint. The custom Query builder class treats values containing parentheses as SQL functions and directly concatenates them into the ORDER BY clause without quoting, bypassing the esc_sql() sanitization. Authenticated attackers with subscriber-level access can exploit this via the 'order' and 'orderby' parameters to extract sensitive database information.

MitigationUpgrade to version 3.7.26 or later which contains the patch. If immediate upgrade is not possible, consider restricting API endpoint access or implementing additional WAF rules as temporary mitigation.

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

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

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

Am I affected?

dbcve checks

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

Verify MasterStudy LMS plugin is installed

In WordPress admin, go to Plugins > Installed Plugins and look for MasterStudy LMS, or check the filesystem under wp-content/plugins/ for the masterstudy-lms directory

Affected if The plugin is not installed on the WordPress site
Identify the installed plugin version

Check the plugin header in wp-content/plugins/masterstudy-lms/main.php for 'Version:' or view the plugin details in WordPress admin Plugins page

Affected if Version is lower than 3.7.26 (the vulnerability is present in versions before the patch)
Confirm the REST API endpoint exists and responds

Send a GET request to /wp-json/lms/stm-lms/order/items or /?rest_route=/lms/stm-lms/order/items

Affected if The endpoint returns a valid response (indicating the plugin component is active)
Check if API authentication is enabled for subscriber-level users

Test accessing the endpoint with a subscriber-level user account using WordPress REST API authentication

Affected if Subscriber-level users can successfully authenticate to the API (indicating the attack vector is accessible)

A site is affected if it runs MasterStudy LMS version lower than 3.7.26 and has the REST API endpoint accessible to subscriber-level authenticated users.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Upgrade to version 3.7.26 or later which contains the patch. If immediate upgrade is not possible, consider restricting API endpoint access or implementing additional WAF rules as temporary mitigation.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing4.0 h
Review / QA2.0 h

15.0 hours of engineering $2,640

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4817 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-4817?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 0.5%

Remediation

Need this fixed?

Have this fixed 15 hrs · Moderate

Typical engagement from $2,640

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-4817 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References