CVE-2026-23799
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 · uneditedMissing Authorization vulnerability in Themeum Tutor LMS tutor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Tutor LMS: from n/a through <= 3.9.5.
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 confidenceMissing Authorization vulnerability in Themeum Tutor LMS allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly verify user permissions before allowing access to certain functionality, potentially enabling unauthorized users to perform actions beyond their intended privileges. This is a broken access control issue affecting versions up to and including 3.9.5.
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
- 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 Tutor LMS is installedLocate the Tutor LMS plugin in your WordPress installation. This is typically found in wp-content/plugins/tutor/ directory. Check for the presence of the plugin files.Affected if Tutor LMS plugin is present in the WordPress environment
-
Identify the installed versionCheck the main plugin file (usually tutor-version.php or the main index.php) for the version constant, or view the installed version shown in WordPress admin under Plugins > Installed Plugins.Affected if The installed version is 3.9.5 or any version prior to it (e.g., 3.9.4, 3.9.0, etc.)
-
Verify user role permission enforcementTest access to administrative functions with a low-privilege user account (e.g., student, subscriber). Attempt actions that should require instructor or administrator privileges, such as modifying course settings, accessing user data, or changing system configurations.Affected if A non-privileged user account can successfully perform actions that should be restricted to instructors or administrators
-
Audit access control configurationsReview the Tutor LMS settings in the WordPress admin panel. Check role capabilities under Users > Users > Tutor LMS Roles (if available) and verify that each user role has only the intended permissions enabled.Affected if User roles have permissions that appear inconsistent with their intended access level, or if unrestricted access settings are found
You are affected if Tutor LMS version 3.9.5 or lower is installed AND the plugin handles user actions without proper permission verification.
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 dataUpdate Tutor LMS to the latest patched version once available. In the interim, restrict user role permissions and review access control configurations. Conduct a thorough audit of authorization checks throughout the plugin.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23799 — 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-23799 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