CVE-2026-42730
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Stylemix MasterStudy LMS masterstudy-lms-learning-management-system allows Blind SQL Injection.This issue affects MasterStudy LMS: from n/a through <= 3.7.29.
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 confidenceA blind SQL injection vulnerability exists in the MasterStudy LMS WordPress plugin (versions up to 3.7.29). The vulnerability allows attackers to inject malicious SQL queries through unsanitized input, potentially enabling data exfiltration or manipulation of the database. The CVSS score of 8.5 indicates high severity due to the potential for unauthorized database access.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the MasterStudy LMS plugin versionAccess your WordPress admin dashboard and navigate to Plugins > Installed Plugins. Find MasterStudy LMS in the list and note the version number displayed. Alternatively, check the main plugin file (typically /wp-content/plugins/masterstudy-lms/main.php) for the 'Version' header in the plugin comments.Affected if The displayed version is 3.7.29 or any version number lower than 3.7.29.
-
Verify the plugin is activeIn the WordPress admin under Plugins > Installed Plugins, confirm that MasterStudy LMS shows as 'Active' rather than 'Inactive' or 'Must Use'.Affected if The plugin is active and the version is 3.7.29 or lower.
-
Confirm WordPress version is not mitigating the vectorCheck your WordPress version under Dashboard > Updates or in the site source. Note that WordPress core version does not directly mitigate plugin SQL injection flaws, but ensures the base platform is current.Affected if No mitigation; this confirms the plugin runs in an active WordPress environment where the vulnerable code executes.
-
Identify accessible endpoints handling user inputReview your web server logs or use a directory scanner to identify publicly accessible AJAX handlers or form endpoints under /wp-admin/admin-ajax.php or similar paths that the MasterStudy LMS plugin registers. These endpoints may process unsanitized parameters.Affected if Publicly accessible endpoints exist that accept user-supplied input through the MasterStudy LMS plugin.
You are affected if MasterStudy LMS is active and the installed version is 3.7.29 or lower, as this version range contains the blind SQL injection vulnerability in unsanitized input handling.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade MasterStudy LMS to the latest version (above 3.7.29) which contains the patched code. If immediate patching is not possible, implement input validation and web application firewall rules to mitigate SQL injection attempts until the update can be applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42730 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42730 in production — separate from our analysis above.
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.
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.
- 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