dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-32223

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Authorization Bypass Through User-Controlled Key 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.4.

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 confidence

Authorization bypass vulnerability in Themeum Tutor LMS allows attackers to bypass access controls by manipulating user-controlled keys, exploiting incorrectly configured access control security levels. The flaw affects versions up to 3.9.4, enabling unauthorized access to protected functions or resources.

MitigationUpdate Tutor LMS to the latest patched version. If no patch is immediately available, review and harden access control logic to properly validate user-controlled keys against expected authorization levels.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Tutor LMS version
    Locate the Tutor LMS plugin in your WordPress installation (wp-content/plugins/tutor) and check the main plugin file header for the 'Version' defined value, or query the WordPress options table for the 'tutor_version' option
    Affected if The installed version is 3.9.4 or lower
  2. Verify access control configuration
    Inspect the Tutor LMS access control settings in the WordPress admin dashboard under Tutor LMS > Settings > General > Role Manager, or examine the source code files in the /tutor/ directory for role and capability checks
    Affected if Custom or misconfigured access control levels exist that rely on user-controlled keys without proper validation
  3. Check for exposed API endpoints
    Review the Tutor LMS REST API routes (typically in /tutor/includes/rest-api/ or /classes/RestApi.php) and verify if endpoints handling sensitive operations validate authorization through user-supplied parameters
    Affected if Protected API endpoints accept user-controlled keys (such as user_id, course_id, or role parameters) without proper capability verification
  4. Inspect permission callbacks
    Examine the permission_callback functions in Tutor LMS REST API route definitions to confirm they validate against expected security levels rather than trusting client-supplied values
    Affected if Permission callbacks rely on user input that can be manipulated to bypass authorization checks

Your environment is affected if Tutor LMS version is 3.9.4 or lower AND the installation uses any custom access control logic or REST API endpoints that validate authorization through user-manipulatable parameters.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Tutor LMS to the latest patched version. If no patch is immediately available, review and harden access control logic to properly validate user-controlled keys against expected authorization levels.

Recommended fix Moderate confidence

Upgrade to the latest version of Tutor LMS (version 3.9.5 or later)

  1. 1. Navigate to your WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find Themeum Tutor LMS in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version of Tutor LMS from the official WordPress repository or Themeum website
  6. 6. After updating, verify that the plugin is functioning correctly by testing the affected functionality

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2025-32223 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