CVE-2023-35093
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 · uneditedBroken Access Control vulnerability in StylemixThemes MasterStudy LMS WordPress Plugin – for Online Courses and Education plugin <= 3.0.8 versions allows any logged-in users, such as subscribers to view the "Orders" of the plugin and get the data related to the order like email, username, and more.
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 confidenceThe MasterStudy LMS WordPress plugin <= 3.0.8 lacks proper authorization checks on its Orders functionality, allowing any authenticated user with subscriber-level privileges to access sensitive order data including customer emails and usernames. This is a classic Broken Access Control / Insecure Direct Object Reference (IDOR) vulnerability where the plugin fails to verify if the requesting user has permission to view order information.
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<= 3.0.8CVSS 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
- 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? 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.
-
Confirm MasterStudy LMS plugin is installedIn WordPress admin, go to Plugins and locate MasterStudy LMS in the list of installed pluginsAffected if Plugin is not installed, no further action needed
-
Determine installed plugin versionClick on the MasterStudy LMS plugin entry to view its details; note the version number shown in the plugin descriptionAffected if Version is 3.0.8 or lower, indicating the vulnerable version
-
Check if WordPress allows new user registrationIn WordPress admin, go to Settings > General and look for the 'Membership' setting 'Anyone can register' - verify whether it is checked or enabledAffected if User registration is enabled, allowing potential attacker to create a subscriber account
-
Identify subscriber-level user accountsIn WordPress admin, go to Users and filter by the Subscriber role, or query the wp_usermeta table for meta_value = 'subscriber'Affected if Any subscriber accounts exist in the system
Environment is affected if MasterStudy LMS plugin version 3.0.8 or lower is installed and WordPress has user registration enabled or already contains subscriber-level accounts, as these conditions enable exploitation of the authorization bypass in the Orders functionality
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.
dbcve · scopedUpdate MasterStudy LMS plugin to version 3.0.9 or later which contains proper authorization controls. Until the update is applied, consider disabling new user registrations or auditing existing user accounts with subscriber roles.
MasterStudy LMS 3.0.9 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find MasterStudy LMS in the plugin list
- Click 'Update now' if an update is available, or manually download the latest version from WordPress.org
- After updating, verify that subscribers can no longer access order data by testing with a low-privilege user account
- Confirm the plugin is running version 3.0.9 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35093 — 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-2023-35093 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