dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13679

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-08
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
The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the get_order_by_id() function in all versions up to, and including, 3.9.3. This makes it possible for authenticated attackers, with Subscriber-level access and above, to enumerate order IDs and exfiltrate sensitive data (PII), such as student name, email address, phone number, and billing address.

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 a broken access control vulnerability where the get_order_by_id() function lacks a capability check, allowing any authenticated user with Subscriber-level access to query order data by ID and exfiltrate sensitive PII including student names, emails, phone numbers, and billing addresses.

MitigationUpdate Tutor LMS to the latest version that includes proper capability checks on the get_order_by_id() function, or implement WordPress capability verification (e.g., current_user_can('manage_options') or similar) before executing the order retrieval logic.

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. Verify Tutor LMS plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/tutor) or view the installed plugins in WordPress admin under Plugins > Installed Plugins. Identify if 'Tutor LMS' appears in the list.
    Affected if Tutor LMS plugin is installed and active on the WordPress site
  2. Determine installed Tutor LMS version
    In WordPress admin, go to Plugins > Installed Plugins and find the Tutor LMS entry to view its version number. Alternatively, check the main plugin file (tutor.php) for the 'Version' header in the plugin comments.
    Affected if The installed version is older than the patched version that includes capability checks on get_order_by_id()
  3. Locate the vulnerable get_order_by_id function
    Examine the Tutor LMS source code, specifically look for the get_order_by_id function in the plugin files (typically in includes/ or classes/ directories). Verify whether the function includes a capability check such as current_user_can() before executing the order retrieval logic.
    Affected if The get_order_by_id function exists and does not contain a capability check (e.g., current_user_can('manage_options') or 'tutor_manage_engineering') before returning order data
  4. Test access with low-privilege user
    Create or use a test user account with the Subscriber role (the minimum role tested in the vulnerability). Attempt to call the get_order_by_id function via the WordPress REST API or AJAX endpoint to retrieve order data for any order ID.
    Affected if A user with Subscriber role can successfully retrieve order details including student PII (names, emails, phone numbers, billing addresses) without authentication errors or permission rejections

A site is affected if Tutor LMS is installed and any authenticated user with Subscriber-level access can retrieve order data without proper capability verification.

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 version that includes proper capability checks on the get_order_by_id() function, or implement WordPress capability verification (e.g., current_user_can('manage_options') or similar) before executing the order retrieval logic.

Recommended fix Moderate confidence

Tutor LMS 3.9.4 or later

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Tutor LMS – eLearning and online course solution' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the version number matches or exceeds the fixed release
Caveat Review plugin settings and course content after update to ensure compatibility

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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