dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-3360

HIGH · 7.5 CVSS v3.1 Published 2026-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to an Insecure Direct Object Reference in all versions up to, and including, 3.9.7. This is due to missing authentication and authorization checks in the `pay_incomplete_order()` function. The function accepts an attacker-controlled `order_id` parameter and uses it to look up order data, then writes billing fields to the order owner's profile (`$order_data->user_id`) without verifying the requester's identity or ownership. Because the Tutor nonce (`_tutor_nonce`) is exposed on public frontend pages, this makes it possible for unauthenticated attackers to overwrite the billing profile (name, email, phone, address) of any user who has an incomplete manual order, by sending a crafted POST request with a guessed or enumerated `order_id`.

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 confidence

The Tutor LMS WordPress plugin has an IDOR vulnerability in the `pay_incomplete_order()` function. The function accepts an attacker-controlled `order_id` parameter without authentication or authorization verification, allowing unauthenticated attackers to overwrite billing profile fields (name, email, phone, address) for any user who has an incomplete manual order. The exposed `_tutor_nonce` on public pages facilitates exploitation.

MitigationApply the vendor patch (version 3.9.8 or later) which adds proper authentication and authorization checks to the `pay_incomplete_order()` function, validating user identity and order ownership before allowing profile updates.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Verify Tutor LMS plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Tutor LMS' or check the file /wp-content/plugins/tutor/ for existence
    Affected if Tutor LMS plugin is not installed on the WordPress site
  2. Determine installed Tutor LMS version
    Check the plugin version in the WordPress plugins list, or read the main plugin file header at /wp-content/plugins/tutor/tutor.php for the 'Version' field
    Affected if The installed version is earlier than 3.9.8 (vulnerable versions)
  3. Check for incomplete manual orders
    Query the WordPress database for orders with status 'pending' or 'incomplete' in the tutor orders table (usually wp_tutor_order_items or similar), or check in Tutor LMS admin under Orders > Incomplete Orders
    Affected if Any incomplete manual orders exist in the system
  4. Verify nonce exposure on public pages
    View the source HTML of any public-facing Tutor LMS page (course catalog, single course) and search for input fields containing '_tutor_nonce'
    Affected if The '_tutor_nonce' hidden field is present in public-facing pages without authentication requirements

The site is affected if Tutor LMS version is below 3.9.8 AND incomplete manual orders exist in the system, making the IDOR in pay_incomplete_order() exploitable.

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

Apply the vendor patch (version 3.9.8 or later) which adds proper authentication and authorization checks to the `pay_incomplete_order()` function, validating user identity and order ownership before allowing profile updates.

Recommended fix Moderate confidence

Tutor LMS version 3.9.8 or later

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate the Tutor LMS plugin and check the current version is 3.9.7 or below
  4. Update the Tutor LMS plugin to version 3.9.8 or later through the WordPress plugin update mechanism, or download the latest version from the WordPress plugin repository
  5. Verify the plugin updated successfully by checking the installed version
  6. Confirm the vulnerability is remediated by testing that the pay_incomplete_order function now requires proper authentication

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3360 — 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-2026-3360 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