CVE-2025-6639
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 Pro – eLearning and online course solution plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.8.3 due to missing validation on a user controlled key when viewing and editing assignments through the tutor_assignment_submit() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to view and edit assignment submissions of other students.
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 Pro WordPress plugin fails to validate user ownership in the tutor_assignment_submit() function. Authenticated users with Subscriber-level access can manipulate assignment IDs to view and modify submissions belonging to other students, due to missing authorization checks on a user-controlled parameter.
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.
-
Identify Tutor LMS Pro versionIn WordPress admin, go to Plugins > Installed Plugins and locate Tutor LMS Pro. The version number is displayed below the plugin name. Alternatively, check the plugin header in /wp-content/plugins/tutor-lms-pro/tutor-pro.php for 'Version:'Affected if Version is lower than 3.8.4 (the fix includes proper authorization validation)
-
Confirm assignment feature is activeCheck if any course on the site has assignments enabled. In Tutor LMS, assignments are created per course. Look for courses with the Assignment addon active or check if /tutor-assignment/ endpoint is accessibleAffected if Assignments are created and accessible; the vulnerability allows unauthorized access to any assignment submission
-
Enumerate subscriber-level usersIn WordPress admin, go to Users > All Users and filter by 'Subscriber' role. Count how many subscriber accounts exist. These users can exploit the flaw with minimal privilegesAffected if Any subscriber-level user accounts exist on the site
-
Review assignment submission access logsCheck server access logs (Apache/nginx) or WordPress activity logs for requests to assignment-related URLs (contains 'assignment_id' parameter) where the user ID does not match the submission owner. Look for patterns like /tutor_assignment_submit/ with manipulated IDsAffected if Logs show assignment access from users who do not own the submission, or unusual assignment_id parameter values
-
Audit assignment submission ownershipQuery the WordPress database: SELECT ID, post_author, post_title FROM wp_posts WHERE post_type = 'tutor_assignment' AND post_status = 'publish'; then compare post_author against any submitted meta. Check if non-owners can access /wp-json/tutor/v1/assignment/submissions?assignment_id=XAffected if Submissions are visible to or modifiable by users who did not create them
The environment is affected if Tutor LMS Pro version is below 3.8.4 AND the site has both active assignments AND subscriber-level users who could exploit the missing authorization check in tutor_assignment_submit().
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 to version 3.8.4 or later which includes proper authorization validation. Until then, limit subscriber-level account creation and monitor for suspicious assignment access patterns.
Upgrade to the latest version of Tutor LMS Pro (version higher than 3.8.3)
- 1. Log in to the WordPress admin dashboard with administrator privileges
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Tutor LMS Pro – eLearning and online course solution' in the plugin list
- 4. Check the current installed version (visible under the plugin name)
- 5. If the installed version is 3.8.3 or below, click 'Update Now' to install the latest available version
- 6. After updating, verify the new version number reflects the update
- 7. Test that assignment submissions can only be viewed and edited by the original submitter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6639 — 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-2025-6639 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