Uncanny Toolkit for LearnDash ≤ 3.8.2: The Login Gate That Looked Up a Different User (CVE-2026-119096, CVSS 9.8)

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Uncanny Toolkit for LearnDash ≤ 3.8.2: The Login Gate That Looked Up a Different User (CVE-2026-119096, CVSS 9.8)

A login form is a contract: the account you check is the account you sign in. CVE-2026-119096 breaks that contract inside Uncanny Toolkit for LearnDash, the companion plugin for LearnDash learning sites. The plugin's verification gate looks up one string; WordPress's sign-on routine acts on a different one — and in the gap between those two lookups, an unauthenticated visitor becomes someone else. The flaw scores CVSS 9.8, and the CVE record names no fixed version yet.

What Happened

CVE-2026-119096 is an authentication bypass in Uncanny Toolkit for LearnDash, disclosed October 31, 2026 (CNA: Wordfence).

Am I Affected?

Check wp-admin → Plugins for Uncanny Toolkit for LearnDash and its version. At 3.8.2 or below, you are in the affected range. LearnDash sites are worth bypassing: they hold student, instructor, and administrator accounts, course content people paid for, and the personal data attached to all of it — and the flaw needs no account of any kind to attempt.

One honesty note, because it is the whole point of how we cover these: our scanner does not claim a version check for this one. The CVE record names no wordpress.org listing we could verify — no directory slug, no readable version disclosure a passive check could key on without guessing. Keying a check to a guessed slug would produce claims we cannot stand behind in either direction. This article exists because the flaw is real and urgent — not because we can detect it passively. What the free mini-scan can do is check the rest of your site's exposed surface while you handle this one by hand.

What To Do Now

  1. Review login activity today. Look at recent sessions and sign-ins for your administrator and instructor accounts; a bypass this quiet leaves no failed-login trail, so unexplained successful logins are the signal.
  2. Audit the accounts themselves. Users → All Users: every Administrator and instructor should be a person you can name, with an email address you recognize. Force a password reset for any account you cannot fully account for.
  3. Update the moment the vendor ships a release naming CVE-2026-119096 — and do not treat an update that does not mention this CVE as a fix for this CVE.
  4. Until that release exists, weigh restricting the plugin — if the toolkit's front-end login features are not load-bearing for your site, disabling them (or the plugin) until a named patch lands is the conservative move for a 9.8 with no fix.

The Bigger Lesson

A check and the action it guards must parse the input the same way. Two parsers, one field, and the gap between them is the vulnerability: the gate normalized nothing, the sign-on normalized everything, and the attacker lived in the difference. When an AI builder writes a verification step in one place and hands the same input to a framework routine somewhere else, "we checked the email" can be literally true and completely useless. Consistency of parsing is not a style preference — it is the security property.

Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the login review finds a stranger.


Running LearnDash with Uncanny Toolkit? Check your version and your login history, then run the free check at preshipit.com/free-scan — it covers the exposures a scan can see, and articles like this one cover the ones it can't.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report