# CVE-2025-64212: WordPress MasterStudy LMS Pro plugin < 4.7.16 - Broken Access Control vulnerability


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-8rwj-g494-3qp6

## What is CVE-2025-64212?

CVE-2025-64212 is a medium-severity vulnerability in StylemixThemes MasterStudy LMS Pro, published on 29 Oct 2025. 

### Official description

Missing Authorization vulnerability in StylemixThemes MasterStudy LMS Pro masterstudy-lms-learning-management-system-pro allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects MasterStudy LMS Pro: from n/a through < 4.7.16.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-64212?


## How do I fix CVE-2025-64212?

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

## Is CVE-2025-64212 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64212 and fix it if it is affected.

What it is: CVE-2025-64212 is a medium-severity vulnerability in StylemixThemes MasterStudy LMS Pro, published on 29 Oct 2025. 
Exploitation: There is no known exploitation of CVE-2025-64212 in the wild and no public exploit code.

Affected product: StylemixThemes MasterStudy LMS Pro. 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-2025-64212/ (Markdown: https://insights.sbomify.com/CVE-2025-64212/index.md)
```

## Sources

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

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