# CVE-2026-63237: TOTP two-factor authentication bypass vulnerability

> Attackers can bypass TOTP two-factor authentication by supplying a client-controlled seed, potentially gaining unauthorized administrator access to Koollab LMS.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-8j44-5653-q846

## What is CVE-2026-63237?

CVE-2026-63237 is a medium-severity authentication bypass vulnerability in Three Learning Koollab LMS, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A TOTP two-factor authentication bypass vulnerability in
Koollab LMS allowed an
attacker to supply a client-controlled seed to generate a matching one-time
password and bypass the second authentication factor, potentially enabling
unauthorised access to administrator accounts.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-63237?


## How do I fix CVE-2026-63237?

No fix has been published for CVE-2026-63237 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63237 being exploited?

There is no known exploitation of CVE-2026-63237 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63237 and fix it if it is affected.

What it is: CVE-2026-63237 is a medium-severity authentication bypass vulnerability in Three Learning Koollab LMS, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-63237 in the wild and no public exploit code.

Affected product: Three Learning Koollab LMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63237/ (Markdown: https://insights.sbomify.com/CVE-2026-63237/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63237
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63237
- OSV: https://osv.dev/vulnerability/CVE-2026-63237

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63237/
Summaries are generated and may contain mistakes; the official description above is the record.