# CVE-2026-80069: MasterStudy LMS WordPress Plugin < 3.7.50 Missing Authorization via stm_lms_send_test_email_ajax


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-hp8j-2mhm-c28w

## What is CVE-2026-80069?

CVE-2026-80069 is a medium-severity vulnerability in Stylemix MasterStudy LMS WordPress Plugin, published on 29 Oct 2026. 

### Official description

MasterStudy LMS plugin for WordPress before 3.7.50 contains a missing authorization vulnerability that allows any authenticated user, including Subscribers, to trigger the stm_lms_send_test_email_ajax AJAX action without capability or nonce validation. Attackers can invoke this handler directly or via cross-site request forgery to cause an uncaught PHP fatal error that, when display_errors is enabled, discloses the absolute filesystem path of the plugin.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-80069 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80069 is a medium-severity vulnerability in Stylemix MasterStudy LMS WordPress Plugin, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-80069 in the wild and no public exploit code.

Affected product: Stylemix MasterStudy LMS WordPress Plugin. 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-80069/ (Markdown: https://insights.sbomify.com/CVE-2026-80069/index.md)
```

## Sources

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

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