# CVE-2026-14310: Tutor LMS < 4.0.0 - Subscriber+ Cross-Course Q&A Content Disclosure and Reply Injection

> Authenticated users can read and inject replies into Q&A threads of courses they do not have access to.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-96xm-q386-833c

## What is CVE-2026-14310?

CVE-2026-14310 is a medium-severity missing authorization vulnerability in Unknown Tutor LMS, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Tutor LMS  WordPress plugin before 4.0.0 does not properly verify that a user has access to the course a Q&A thread belongs to before returning or writing to that thread, allowing authenticated users with subscriber-level access and above who can access any single course to read the Q&A threads of other courses and to inject replies into them.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-14310 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14310 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14310 is a medium-severity missing authorization vulnerability in Unknown Tutor LMS, published on 30 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14310 exists.

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-14310/ (Markdown: https://insights.sbomify.com/CVE-2026-14310/index.md)
```

## Sources

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

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