dbcve.org
VulnerabilityAwaiting classification

CVE-2026-12275

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click 6 weeks old

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 WordPress plugin before 3.9.13 does not, in its Droip and Kirki page-builder integration, perform the enrollment, purchase, and private-course capability checks it enforces in its core course handler, allowing authenticated users with subscriber-level access to enroll in paid or private courses without authorization, read private course content, and mark arbitrary courses as completed, on sites where the Droip or Kirki integration is active.

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 before 3.9.13 lacks proper authorization checks in its Droip and Kirki page-builder integration. Authenticated users with subscriber-level access can bypass the capability checks enforced in the core course handler, enabling unauthorized enrollment in paid or private courses, access to private course content, and arbitrary course completion marking.

MitigationUpgrade Tutor LMS to version 3.9.13 or later to receive the patched integration that implements proper enrollment, purchase, and private-course capability checks matching the core handler.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/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 WordPress plugin directory for tutor-lms version. In WordPress admin, go to Plugins > Installed Plugins and look for TutorLMS, or inspect the main plugin file header for 'Version:' tag.
    Affected if The installed version is below 3.9.13 (e.g., 3.9.12, 3.9.11, 3.0.0, etc.) or the version field is missing/unreadable.
  2. Confirm Droip page builder integration status
    Check WordPress admin for Droip plugin presence and any Tutor LMS settings that enable Droip integration. Look under Tutor LMS > Settings for any page builder integration options.
    Affected if Droip plugin is installed AND Tutor LMS integration with Droip is enabled or active in the environment.
  3. Confirm Kirki page builder integration status
    Check WordPress admin for Kirki plugin presence. Inspect Tutor LMS settings for any Kirki-related options or customizer integrations.
    Affected if Kirki plugin is installed AND Tutor LMS uses or connects to Kirki for course display or settings.
  4. Review user role configuration
    Navigate to WordPress Users > Roles or use a role management tool to identify if any subscriber-level roles exist and whether they have been granted elevated course permissions beyond default.
    Affected if Subscriber-level accounts exist and the site allows subscriber users to access course-related functionality.
  5. Audit course enrollment and completion records
    Query the database for enrollment records where user_id belongs to a subscriber-role account, or review course completion logs for unexpected completions by low-privilege users.
    Affected if Subscriber users appear enrolled in paid courses, can access private course content, or have course completion records they did not legitimately obtain.

A site is affected if Tutor LMS version is below 3.9.13 AND the Droip or Kirki page-builder integrations are in use while subscriber-level users can access course functionality.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Tutor LMS to version 3.9.13 or later to receive the patched integration that implements proper enrollment, purchase, and private-course capability checks matching the core handler.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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