# CVE-2026-40314: NamelessMC: Reactions on private or blocking profile posts can be read and modified without proper authorization

> Unauthenticated users can read private profile reactions, and low-privileged users can modify them, bypassing visibility restrictions in NamelessMC.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/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:** 2 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-55q9-8qm3-4grc

## What is CVE-2026-40314?

CVE-2026-40314 is a medium-severity missing authorization vulnerability in NamelessMC Nameless, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NamelessMC is website software for Minecraft servers. In version 2.2.4,`core/classes/Misc/ProfilePostReactionContext.php` only verifies that the wall post exists and does not enforce blocked/private-profile visibility. `modules/Core/queries/reactions.php` allows unauthenticated GET requests for reaction details. This means that unauthenticated visitors can read reaction participants and timestamps for private profile posts and uthenticated low-privileged users can add reactions to private or blocking profile posts. Version 2.2.5 fixes the issue.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-40314 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40314 is a medium-severity missing authorization vulnerability in NamelessMC Nameless, published on 2 Jun 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-40314 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-2026-40314/ (Markdown: https://insights.sbomify.com/CVE-2026-40314/index.md)
```

## Sources

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

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