Masterstudy LmsWordPress extension · Stylemixthemes

CVE-2023-35090

MEDIUM · 5.4 CVSS v3.1 Published 2023-06-22
Fix available
A fix is available. Upgrade to after 3.0.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in StylemixThemes MasterStudy LMS WordPress Plugin – for Online Courses and Education plugin <= 3.0.7 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

Authenticated contributor+ users can inject malicious JavaScript through the MasterStudy LMS plugin that gets stored in the database and executes when other users view the affected content. This is a stored XSS vulnerability stemming from insufficient input sanitization and output encoding in plugin functions.

MitigationUpdate MasterStudy LMS plugin to version 3.0.8 or later. Until patched, restrict contributor-level user permissions and monitor for suspicious script injections in course content.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Masterstudy LmsWordPress extension
Affected:<= 3.0.7

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

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

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 plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'MasterStudy LMS' in the installed plugins list
    Affected if MasterStudy LMS plugin is present in the WordPress installation
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find MasterStudy LMS and note the version number displayed
    Affected if Version is 3.0.7 or lower
  3. Identify user roles with contributor access
    Go to WordPress admin > Users and review user accounts for any with 'Contributor' role or higher who have access to create or edit course content
    Affected if One or more contributor-level or higher user accounts exist with access to course/content creation
  4. Inspect course content for suspicious scripts
    Review course titles, descriptions, and lesson content in the MasterStudy LMS course editor for any unexpected <script> tags, javascript: URLs, or event handlers (onclick, onerror, etc.) stored in the database
    Affected if Malicious JavaScript code is found embedded in any course, lesson, or course content fields
  5. Check database for injected XSS payloads
    Query the WordPress database (wp_posts table) for course-related post types (stm-courses, stm-lessons) containing HTML script tags or encoded JavaScript patterns using: SELECT * FROM wp_posts WHERE post_type IN ('stm-courses','stm-lessons') AND post_content LIKE '%<script%'
    Affected if Database contains stored script tags or JavaScript in course-related post content

You are affected if MasterStudy LMS plugin version 3.0.7 or lower is installed AND contributor-level user accounts have access to create course content, or if suspicious scripts are already present in course data.

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
Upgrade available Upgrade to a release after 3.0.7
Interim mitigation

Update MasterStudy LMS plugin to version 3.0.8 or later. Until patched, restrict contributor-level user permissions and monitor for suspicious script injections in course content.

Recommended fix Moderate confidence

MasterStudy LMS version 3.0.8 or latest available version

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find MasterStudy LMS plugin
  4. Check if update to version 3.0.8 or higher is available
  5. If update available, click 'Update Now' to install the patched version
  6. If no update shown, manually download latest version from WordPress.org or StylemixThemes and upload via Plugins > Add New > Upload Plugin

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

Fix this in Masterstudy Lms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35090 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-35090 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