# CVE-2026-19094: Tutor LMS < 4.0.6 - Unauthenticated SQLi via 'offset' and 'item_per_page' Parameters


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-ch2m-mj23-v6w4

## What is CVE-2026-19094?

CVE-2026-19094 is a medium-severity vulnerability in Unknown Tutor LMS, published on 26 Aug 2026. 

### Official description

The Tutor LMS  WordPress plugin before 4.0.6 does not validate values used to build a database query, and does not restrict which template file a request may load, allowing unauthenticated users to inject SQL and to read question and answer content belonging to courses that are not publicly available.

The injected text reaches the query as grammar rather than as data, and on the database engines tested it does not yield extraction of arbitrary data, so the confidentiality impact is the disclosed course content rather than the database at large.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-19094 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19094 is a medium-severity vulnerability in Unknown Tutor LMS, published on 26 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-19094 in the wild and no public exploit code.

Affected product: Unknown Tutor 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-19094/ (Markdown: https://insights.sbomify.com/CVE-2026-19094/index.md)
```

## Sources

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

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