dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-0953

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Pro plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 3.9.5 via the Social Login addon. This is due to the plugin failing to verify that the email provided in the authentication request matches the email from the validated OAuth token. This makes it possible for unauthenticated attackers to log in as any existing user, including administrators, by supplying a valid OAuth token from their own account along with the victim's email 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 Pro plugin's Social Login addon fails to validate that the email address submitted during OAuth authentication matches the email embedded in the OAuth provider's validated token. An attacker with a valid OAuth token (e.g., from their own Google or Facebook login) can supply any victim's email address and successfully authenticate as that user, including administrative accounts.

MitigationUpdate Tutor LMS Pro to a version beyond 3.9.5 that implements proper email-to-OAuth-token validation, or temporarily disable the Social Login addon until a patch is available.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Pro version
    Navigate to WordPress admin > Plugins > Installed Plugins > Tutor LMS Pro, or check the plugin header file for the 'Version' field
    Affected if Version is 3.9.5 or lower, or if the version cannot be determined (indicating an old installation)
  2. Confirm Social Login addon is active
    Go to WordPress admin > Tutor LMS > Addons, or inspect the plugin directory for 'tutor-social-login' folder and check if it's enabled in the database options table
    Affected if The Social Login addon is listed as active or the addon folder exists and is loaded
  3. Verify OAuth providers are configured
    Check WordPress admin > Tutor LMS > Settings > Social Login, or inspect the wp_options table for keys containing 'tutor_social_login' or provider-specific settings (e.g., 'tutor_google_config', 'tutor_facebook_config')
    Affected if At least one OAuth provider (Google, Facebook, etc.) has API credentials configured and enabled
  4. Check for OAuth authentication endpoints
    Inspect network traffic or server logs for requests to /wp-json/tutor/v1/social_login/* endpoints, or check the site's rewrite rules for tutor social login routes
    Affected if OAuth-based authentication requests are being processed by the site

A site is affected if it runs Tutor LMS Pro version 3.9.5 or lower, has the Social Login addon enabled, and has at least one OAuth provider configured for user authentication.

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 Pro to a version beyond 3.9.5 that implements proper email-to-OAuth-token validation, or temporarily disable the Social Login addon until a patch is available.

Recommended fix Moderate confidence

Tutor LMS Pro version 3.9.6 or latest available version

  1. Check the current version of Tutor LMS Pro plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in WordPress admin to verify the installed version
  3. Visit the official Tutor LMS website (tutorlms.com) or the WordPress plugin repository to identify the latest available version
  4. Upgrade the Tutor LMS Pro plugin to the latest version available, which should be version 3.9.6 or higher
  5. After upgrading, verify that the Social Login addon is functioning correctly with the new version
  6. Consider reviewing user accounts, especially administrative accounts, for any unauthorized access that may have occurred

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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