dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-63229

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-29
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 3 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
A pre-authentication blind SQL injection vulnerability in Koollab LMS allowed an unauthenticated attacker to use a time-based SQL oracle via the SSO OAuth endpoint to read sensitive database contents, including personally identifiable information, credentials, and valid JWT tokens that may enable account takeover.

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

A pre-authentication blind SQL injection vulnerability exists in the Koollab LMS SSO OAuth endpoint. Attackers can exploit a time-based SQL oracle without credentials to extract sensitive data including PII, credentials, and valid JWT tokens from the database.

MitigationImmediate remediation requires parameterized queries or prepared statements in the OAuth endpoint to eliminate SQL injection vectors. Organizations should also rotate exposed credentials and tokens, implement a WAF with SQLi rules, and audit for additional injection points.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Identify Koollab LMS installation
    Locate the Koollab LMS application directory or service. Common locations include /opt/koollab, /var/www/koollab, or the application's installation folder. Check for the presence of 'koollab', 'koolware', or 'lms' in directory names or running processes.
    Affected if Koollab LMS software is present in the environment
  2. Verify SSO OAuth endpoint is enabled
    Inspect the application configuration files (typically config.php, app.config, or settings.json in the installation directory) for OAuth/SSO-related settings. Look for keys containing 'oauth', 'sso', 'saml', or 'authentication'. Check if these endpoints are exposed in any web server configuration.
    Affected if SSO OAuth endpoint is configured and accessible
  3. Check installed version
    Locate version information in the application's configuration, README, composer.json, package.json, or a dedicated VERSION file within the Koollab LMS installation directory. Compare against any documented version ranges.
    Affected if Installed version falls within an affected range or cannot be determined
  4. Inspect OAuth endpoint source code for SQL injection vulnerabilities
    Examine the source code handling the OAuth endpoint, typically found in files related to 'oauth', 'auth', 'saml', or 'login' within the application's controllers or handlers directory. Search for direct string concatenation in database queries, lack of parameterized queries, or unsanitized user input flowing into SQL statements.
    Affected if Database queries in OAuth handler use string concatenation or direct interpolation without parameterized queries
  5. Test OAuth endpoint for time-based SQL injection response
    Send crafted requests to the OAuth endpoint with SQL injection payloads in parameters such as redirect_uri, client_id, or username. Monitor for time delays in response (sleep commands in SQL). This should only be performed in authorized test environments.
    Affected if The endpoint exhibits delayed responses consistent with time-based SQL injection payloads

A user is affected if Koollab LMS with SSO OAuth is installed, the OAuth endpoint is exposed, and the application uses non-parameterized queries in the OAuth handler, allowing unauthenticated SQL injection.

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

Immediate remediation requires parameterized queries or prepared statements in the OAuth endpoint to eliminate SQL injection vectors. Organizations should also rotate exposed credentials and tokens, implement a WAF with SQLi rules, and audit for additional injection points.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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