# CVE-2025-10038: Binary MLM Plan <= 3.0 - Unauthenticated Limited Privilege Escalation

> Unauthenticated attackers can register to gain manage_bmp capability, allowing them to modify plugin settings.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 15 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q2fx-pxmp-7f63

## What is CVE-2025-10038?

CVE-2025-10038 is a medium-severity vulnerability in letscms Binary MLM Plan, published on 15 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Binary MLM Plan plugin for WordPress is vulnerable to limited Privilege Escalation in all versions up to, and including, 3.0. This is due to bmp_user role granting all users with the manage_bmp capability by default upon registration through the plugin's form. This makes it possible for unauthenticated attackers to register and manage the plugin's settings.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-10038 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10038 is a medium-severity vulnerability in letscms Binary MLM Plan, published on 15 Oct 2025. 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-2025-10038 in the wild and no public exploit code.

Affected product: letscms Binary MLM Plan. 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-10038/ (Markdown: https://insights.sbomify.com/CVE-2025-10038/index.md)
```

## Sources

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

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