dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-1371

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 Sensitive Information Exposure in all versions up to, and including, 3.9.5. This is due to missing authorization checks in the `ajax_coupon_details()` function, which only validates nonces but does not verify user capabilities. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve sensitive coupon information including coupon codes, discount amounts, usage statistics, and course/bundle applications.

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 plugin for WordPress contains a broken access control vulnerability in the ajax_coupon_details() function. The function validates nonces (anti-CSRF tokens) but fails to verify user capabilities before returning sensitive coupon data, allowing any authenticated user with Subscriber-level access or higher to retrieve coupon codes, discount amounts, usage statistics, and course/bundle application details.

MitigationUpdate to version 3.9.6 or later, which should include proper capability checks (e.g., current_user_can('manage_options')) in the ajax_coupon_details() function to verify authorization before exposing coupon data.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 installation and version
    Check the installed Tutor LMS plugin version in WordPress (wp-admin/plugins.php or via WP-CLI: wp plugin list --name=tutor-lms)
    Affected if Version is earlier than 3.9.6 or version cannot be determined but the plugin is active
  2. Locate the ajax_coupon_details function
    Search the Tutor LMS plugin files for the ajax_coupon_details function definition (typically in includes/ajax.php or similar)
    Affected if The function exists in the installed version
  3. Verify absence of capability check
    Examine the ajax_coupon_details function code - look for missing current_user_can() or similar authorization calls before returning coupon data
    Affected if The function returns coupon data without verifying user capabilities (e.g., no current_user_can('manage_options') or 'edit_courses' check present)
  4. Confirm subscriber-level access is sufficient
    Review the function to verify it only validates nonces but not user roles/permissions
    Affected if The function validates nonces but accepts any authenticated session without role verification

A user is affected if Tutor LMS is installed with a version earlier than 3.9.6 AND the ajax_coupon_details function lacks proper capability checks before exposing coupon data.

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 to version 3.9.6 or later, which should include proper capability checks (e.g., current_user_can('manage_options')) in the ajax_coupon_details() function to verify authorization before exposing coupon data.

Recommended fix Moderate confidence

Tutor LMS version 3.9.6 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Tutor LMS' in the plugin list
  4. Check if current version is 3.9.5 or earlier
  5. If vulnerable, click 'Update Now' to upgrade to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/tutor/ and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the version number reflects the upgrade

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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