dbcve.org
VulnerabilityAwaiting classification

CVE-2026-12274

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
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 verify that the requesting user is allowed to edit a target post before overwriting it in one of its content-builder save handlers, authorizing the request only against an unrelated identifier, allowing authenticated users with instructor-level access to overwrite and take over any post or page on the site, including those owned by administrators.

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 before version 3.9.13 contains an Insecure Direct Object Reference (IDOR) vulnerability in its content-builder save handlers. The plugin fails to verify that the authenticated user has edit permissions for the target post, instead only checking authorization against an unrelated identifier. This allows any authenticated instructor-level user to overwrite arbitrary posts and pages on the WordPress site, including those owned by administrators.

MitigationUpdate Tutor LMS to version 3.9.13 or later which implements proper authorization verification. If immediate update is not possible, temporarily revoke instructor-level permissions and audit recent content changes for unauthorized modifications.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Check installed Tutor LMS version
    Go to WordPress dashboard > Plugins > Installed Plugins, locate Tutor LMS, and note the version number displayed. Alternatively, check the plugin file header in wp-content/plugins/tutor/tutor.php for 'Version:' value.
    Affected if The installed version is lower than 3.9.13 (e.g., 3.9.12, 3.9.10, etc.)
  2. Verify content-builder module is active
    Navigate to WordPress dashboard > Tutor LMS > Settings > General. Look for Content Builder or Course Builder settings. Check if the builder functionality is enabled for instructors.
    Affected if The content-builder feature is enabled and the plugin version is below 3.9.13
  3. Identify instructor-level user accounts
    Go to WordPress dashboard > Users. Look for users assigned the 'Instructor' or 'Tutor Instructor' role. Note the number of instructor accounts present on the site.
    Affected if One or more instructor-level user accounts exist and the plugin version is below 3.9.13
  4. Audit recent post/page modifications
    In WordPress dashboard, go to Posts or Pages list. Sort by 'Modified' date. Check if any posts or pages were recently updated by instructor-level users, especially posts outside their own courses.
    Affected if Posts or pages owned by administrators or other users were modified recently by instructor accounts, and the plugin version is below 3.9.13
  5. Review user capabilities for instructors
    Navigate to Users > Roles (or use a role editor plugin). Examine the Instructor role capabilities. Specifically check if instructors have 'edit_others_posts' or similar broad editing capabilities.
    Affected if Instructor role has elevated edit capabilities beyond their own content, and the plugin version is below 3.9.13

The environment is affected if Tutor LMS version is below 3.9.13, the content-builder module is enabled, and at least one instructor-level user account exists on the WordPress site.

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 version 3.9.13 or later which implements proper authorization verification. If immediate update is not possible, temporarily revoke instructor-level permissions and audit recent content changes for unauthorized modifications.

Recommended fix Moderate confidence

Tutor LMS version 3.9.13 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Tutor LMS in the plugin list
  4. Check the current version number to confirm it is below 3.9.13
  5. Click 'Update Now' if an update is available, or manually download version 3.9.13 from the WordPress plugin repository and upload it
  6. After updating, verify the version number shows 3.9.13 or higher
  7. Test that instructor-level users can only modify their own posts and not posts owned by administrators

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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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