Authenticated profile-wall writes via premature request handling
Published Jun 2, 2026 · Updated Jun 2, 2026
Authorization bypass in NamelessMC Nameless 2.2.4 allows remote authenticated users to write posts through restricted profile URLs. The profile page handles new_post and reply actions before checking CAN_VIEW, while the reply branch verifies only that a target post ID exists rather than that it belongs to the displayed profile. The profile.post permission is required; the flaw permits content insertion into private or blocked profiles and unrelated wall-post threads.
Summary
What happened
Authorization bypass in NamelessMC Nameless 2.2.4 allows remote authenticated users to write posts through restricted profile URLs. The profile page handles new_post and reply actions before checking CAN_VIEW, while the reply branch verifies only that a target post ID exists rather than that it belongs to the displayed profile. The profile.post permission is required; the flaw permits content insertion into private or blocked profiles and unrelated wall-post threads.
The record
- CVE
- CVE-2026-35447
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- NamelessMC
- Product
- Nameless
- Classifications
- CWE-201, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 2026CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion== 2.2.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory profile-wall proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo