# CVE-2025-13618: Mentoring <= 1.2.8 - Unauthenticated Privilege Escalation in mentoring_process_registration

> Unauthenticated attackers can register as administrators due to improper role restriction in the Mentoring plugin registration process.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-28c2-5wc6-j4hm

## What is CVE-2025-13618?

CVE-2025-13618 is a critical vulnerability in dreamstechnologies Mentoring, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Mentoring plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 1.2.8. This is due to the plugin not properly restricting the roles that users can register with in the mentoring_process_registration() function. This makes it possible for unauthenticated attackers to register with administrator-level user accounts.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2025-13618 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13618 is a critical vulnerability in dreamstechnologies Mentoring, published on 5 May 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-2025-13618 in the wild and no public exploit code.

Affected product: dreamstechnologies Mentoring. 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-13618/ (Markdown: https://insights.sbomify.com/CVE-2025-13618/index.md)
```

## Sources

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

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