# CVE-2026-86446: LearnPress 4.4.3 - 4.4.6 - Unauthenticated Quiz Answer Disclosure via check-answer REST Endpoint

> Unauthenticated attackers can retrieve correct quiz answers and explanations for courses configured to allow access without enrollment.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/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:** 17 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-2848-wq6m-p5gf

## What is CVE-2026-86446?

CVE-2026-86446 is a low-severity vulnerability in Unknown LearnPress, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The LearnPress  WordPress plugin before 4.4.7 does not restrict the correctness flags it returns when a quiz answer is checked, allowing unauthenticated attackers to obtain the correct answer to every option of a question, along with the instructor's explanation, on courses configured to be taken without enrolling.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-86446 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86446 is a low-severity vulnerability in Unknown LearnPress, published on 17 Sep 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-86446 in the wild and no public exploit code.

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

## Sources

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

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