# CVE-2026-35447: Missing authorization in Nameless

> Attackers can bypass profile privacy settings to write wall posts and inject replies into arbitrary profiles due to missing authorization checks.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-c9xj-rxgw-g2hq

## What is CVE-2026-35447?

CVE-2026-35447 is a medium-severity missing authorization vulnerability in NamelessMC Nameless, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NamelessMC is website software for Minecraft servers. In version 2.2.4, the profile page (modules/Core/pages/profile.php) processes wall post submissions and replies before verifying whether the viewer is authorized to access the profile. This allows any user with the profile.post permission to write wall posts to private or blocking profiles. Additionally, the reply branch does not verify that the target wall post belongs to the current profile, enabling attackers to inject replies into arbitrary wall posts owned by other profiles via a restricted profile URL. This is patched in version 2.2.5.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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


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

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

## Is CVE-2026-35447 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-35447 is a medium-severity missing authorization vulnerability in NamelessMC Nameless, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35447 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-35447/ (Markdown: https://insights.sbomify.com/CVE-2026-35447/index.md)
```

## Sources

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

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