# CVE-2025-22144: Account Takeover in NamelessMC

> Attackers can take over user accounts by exploiting a flaw in the password reset logic triggered by manual admin validation.

- **Severity:** Critical 9.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2025
- **Updated:** 13 Jan 2025
- **Also known as:** GHSA-p883-7496-x35p

## What is CVE-2025-22144?

CVE-2025-22144 is a critical vulnerability in NamelessMC Nameless, published on 13 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NamelessMC is a free, easy to use & powerful website software for Minecraft servers. A user with admincp.core.emails or admincp.users.edit permissions can validate users and an attacker can reset their password. When the account is successfully approved by email the reset code is NULL, but when the account is manually validated by a user with admincp.core.emails or admincp.users.edit permissions then the reset_code will no longer be NULL but empty. An attacker can request http://localhost/nameless/index.php?route=/forgot_password/&c= and reset the password. As a result an attacker may compromise another users password and take over their account. This issue has been addressed in release version 2.1.3 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password), CWE-610 (Externally Controlled Reference to a Resource in Another Sphere)

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

It affects 1 product.


Products: Namelessmc Nameless.

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

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

## Is CVE-2025-22144 being exploited?

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

## Other vulnerabilities in NamelessMC Nameless

- [CVE-2022-2821](https://insights.sbomify.com/CVE-2022-2821/): Missing Critical Step in Authentication in namelessmc/nameless (critical 9.8)
- [CVE-2025-54117](https://insights.sbomify.com/CVE-2025-54117/): NamelessMC allows Stored Cross-Site Scripting (XSS) in dashboard text editor (critical 9.1)
- [CVE-2025-32389](https://insights.sbomify.com/CVE-2025-32389/): NamelessMC Vulnerable to SQL Injections in /user/messaging and /panel/users/reports Pages (high 8.6)
- [CVE-2025-29784](https://insights.sbomify.com/CVE-2025-29784/): NamelessMC Has Lack of Length Validation for s Parameter in GET Requests (high 7.5)
- [CVE-2025-30357](https://insights.sbomify.com/CVE-2025-30357/): NamelessMC Forum Topic Deletion Triggered by Unrelated User Deletion (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22144 is a critical vulnerability in NamelessMC Nameless, published on 13 Jan 2025. 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-2025-22144 exists.

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

## Sources

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

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