CVE-2026-3358
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 · uneditedThe Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to unauthorized private course enrollment in all versions up to, and including, 3.9.7. This is due to missing post_status validation in the `enroll_now()` and `course_enrollment()` functions. Both enrollment endpoints verify the nonce, user authentication, and whether the course is purchasable, but fail to check if the course has a `private` post_status. This makes it possible for authenticated attackers with Subscriber-level access or above to enroll in private courses by sending a crafted POST request with the target course ID. The enrollment record is created in the database and the private course title and enrollment status are exposed in the subscriber's dashboard, though WordPress core access control prevents the subscriber from viewing the actual course content (returns 404). Enrollment in private courses should be restricted to users with the `read_private_posts` capability.
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 Tutor LMS WordPress plugin fails to validate the post_status of courses before processing enrollment requests. The enroll_now() and course_enrollment() functions verify nonce, authentication, and purchasability but skip checking if the course is marked as 'private'. This allows any authenticated user with Subscriber-level access to enroll in private courses via crafted POST requests, exposing course titles and enrollment records in their dashboard.
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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Tutor LMS plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate TutorLMS, then check the version number. Alternatively, inspect the plugin file header in wp-content/plugins/tutor/tutor.phpAffected if The installed version matches the affected range (verify against official TutorLMS security advisories for this CVE)
-
Identify private courses in the systemQuery the WordPress database: SELECT ID, post_title, post_status FROM wp_posts WHERE post_type = 'courses' AND post_status = 'private'; Or use WP CLI: wp post list --post_type=courses --post_status=privateAffected if There are courses with post_status set to 'private'
-
Verify presence of low-privileged user accountsCheck for users with Subscriber role: In WordPress admin go to Users > All Users and filter by 'Subscriber' role, or query: SELECT user_id, display_name FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%subscriber%';Affected if There is at least one user with Subscriber-level access
-
Inspect enrollment records for private course accessCheck enrollment tables for private course enrollments. Query enrollment records linking private course IDs to subscriber users: SELECT * FROM wp_tutor_enrollments WHERE course_id IN (SELECT ID FROM wp_posts WHERE post_type='courses' AND post_status='private');Affected if Any private course has enrollment records, indicating unauthorized access occurred
-
Review vulnerable enrollment functionsExamine the plugin source code for enroll_now() and course_enrollment() functions in tutor/tutor.php or includes/enrollment.php. Look for missing post_status validation before processing enrollmentAffected if The code lacks post_status='publish' or 'read_private_posts' capability checks before allowing enrollment
A user is affected if Tutor LMS is installed with private courses AND low-privilege subscriber accounts exist AND those subscribers have enrollment records for private courses, indicating the access control bypass was exploited.
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 · scopedAdd post_status validation requiring the 'read_private_posts' capability before allowing enrollment, and restrict private course enrollment to privileged users only.
latest version available in WordPress Plugin Repository (newer than 3.9.7)
- 1. Log in to the WordPress admin dashboard with administrator privileges
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Tutor LMS – eLearning and online course solution' in the plugin list
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Alternatively, download the latest version from the WordPress Plugin Repository at wordpress.org/plugins/tutor/ and upload it manually via Plugins > Add New > Upload Plugin
- 6. After updating, verify the version number reflects the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3358 — 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-3358 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