# CVE-2026-13332: Masteriyo LMS < 2.3.1 - Unauthenticated Arbitrary User Session Termination (Denial of Service)

> Unauthenticated attackers can force-logout any user, including administrators, by exploiting missing authorization checks in an AJAX action.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 27 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-h98r-h4wc-7hjr

## What is CVE-2026-13332?

CVE-2026-13332 is a critical missing authorization vulnerability in Unknown Masteriyo LMS, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Masteriyo LMS  WordPress plugin before 2.3.1 does not correctly verify authorization on an unauthenticated AJAX action used to clear user sessions, allowing unauthenticated attackers to terminate the active sessions (force-logout) of any user on the site, including administrators.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-13332 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-13332 is a critical missing authorization vulnerability in Unknown Masteriyo LMS, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13332 exists.

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

## Sources

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

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