CVE-2026-33398
Information Disclosure in NamelessMC Forums
Publication date: 2026-06-02
Last updated on: 2026-06-02
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| namelessmc | namelessmc | to 2.2.5 (exc) |
| namelessmc | namelessmc | 2.2.5 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-285 | The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in NamelessMC website software for Minecraft servers, specifically in versions prior to 2.2.5. The issue is in the forum module where the endpoint `/forum/get_quotes` only checks if a user is logged in but does not enforce proper access control checks for forum or topic permissions.
Because of this, any authenticated user with low privileges can enumerate post IDs and read content from posts in hidden, private, or staff-only forums that they should not have access to. The normal forum topic page enforces these permissions correctly, but this endpoint does not, leading to improper authorization.
This vulnerability is classified under CWE-285 (Improper Authorization) and was fixed in version 2.2.5 by applying the correct authorization checks.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing unauthorized access to sensitive or restricted forum content. Low-privileged authenticated users can read posts from hidden, private, or staff-only forums, potentially exposing confidential information.
Such unauthorized data exposure can lead to information leakage, loss of privacy, and could undermine trust in the security of your forum or website.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing whether low-privileged authenticated users can access hidden, private, or staff-only forum posts via the `/forum/get_quotes` endpoint. Since the endpoint only checks if the user is logged in but does not enforce forum or topic ACLs, an attacker can enumerate post IDs and retrieve restricted content.
To detect this on your system, you can perform authenticated HTTP requests to the `/forum/get_quotes` endpoint with different post IDs and verify if content from restricted forums is returned.
- Use a tool like curl or wget to send authenticated requests to `/forum/get_quotes` with various post IDs.
- Example curl command: curl -b cookies.txt "https://your-namelessmc-site.com/forum/get_quotes.php?post=POST_ID"
- Replace POST_ID with different post identifiers, including those from hidden or private forums, to check if unauthorized content is accessible.
- Monitor responses for content that should be restricted, indicating the vulnerability is present.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows low-privileged authenticated users to access hidden, private, or staff-only forum posts without proper authorization checks. Such unauthorized access to restricted content could lead to exposure of sensitive or personal information.
Exposure of sensitive data due to improper access controls can potentially violate data protection regulations such as GDPR or HIPAA, which require strict controls on access to personal or sensitive information.
Therefore, this vulnerability may negatively impact compliance with common standards and regulations that mandate proper authorization and protection of sensitive data.
What immediate steps should I take to mitigate this vulnerability?
The immediate and recommended mitigation is to upgrade NamelessMC to version 2.2.5 or later, where the vulnerability has been fixed by enforcing proper authorization checks on the `/forum/get_quotes` endpoint.
Until you can upgrade, consider restricting access to the `/forum/get_quotes` endpoint to trusted users only or disabling it if possible.
Additionally, review and tighten forum and topic access control lists (ACLs) to ensure unauthorized users cannot enumerate or access restricted posts.