dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-33398

HIGH · 7.1 CVSS v4.0 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NamelessMC is website software for Minecraft servers. In version 2.2.4, `modules/Forum/pages/forum/get_quotes.php` only checks whether the caller is logged in, then reads a post by attacker-controlled `post` ID and returns its content. The backend helper in `modules/Forum/classes/Forum.php` does not enforce forum or topic ACLs. In contrast, the normal topic page in `modules/Forum/pages/forum/view_topic.php` enforces forum visibility and `view_other_topics`. Any low-privileged authenticated user can enumerate post IDs and read content from hidden, private, or staff-only forums. Version 2.2.5 fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IDOR vulnerability in NamelessMC 2.2.4's forum quote retrieval endpoint (get_quotes.php). The endpoint only verifies user authentication but fails to enforce forum/topic access control lists, allowing any authenticated user to read posts from private, hidden, or staff-only forums by manipulating the post ID parameter.

MitigationUpgrade to NamelessMC version 2.2.5 which implements proper ACL enforcement for the get_quotes.php endpoint, matching the access controls already present in view_topic.php.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify NamelessMC installation version
    Locate the core version file in your NamelessMC installation (typically version.php or similar in the root/includes directory) and read the version number defined there
    Affected if The installed version is exactly 2.2.4 (or any version between 2.0.0 and 2.2.4 inclusive, as the fix was released in 2.2.5)
  2. Locate the get_quotes.php endpoint
    Search the NamelessMC web root for the file get_quotes.php, commonly found in the /core/ or /includes/ directory structure
    Affected if The file exists in the installation and the version is vulnerable
  3. Verify the endpoint accepts post ID parameters
    Review the get_quotes.php source code to confirm it accepts a post ID parameter (such as 'post' or 'id') and retrieves post content based on that input without additional ACL validation
    Affected if The script processes post ID parameters without checking forum/topic ACL permissions
  4. Check for authenticated user access path
    Confirm that get_quotes.php requires user authentication (logged-in status) but does not enforce forum visibility or topic access restrictions beyond that authentication check
    Affected if The endpoint only validates authentication but allows access to posts from restricted forums when the post ID is known

You are affected if your NamelessMC installation is version 2.2.4 or earlier and contains the get_quotes.php endpoint that only validates user login status without enforcing forum/topic ACL restrictions on the requested post.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to NamelessMC version 2.2.5 which implements proper ACL enforcement for the get_quotes.php endpoint, matching the access controls already present in view_topic.php.

Recommended fix High confidence

NamelessMC version 2.2.5

  1. 1. Create a full backup of the NamelessMC installation including database and files
  2. 2. Download NamelessMC version 2.2.5 from the official GitHub repository or release page
  3. 3. Extract the upgrade package and replace the existing files with the new version
  4. 4. Specifically ensure modules/Forum/pages/forum/get_quotes.php and modules/Forum/classes/Forum.php are updated to the fixed versions
  5. 5. Run any database migrations if included in the upgrade
  6. 6. Clear any caches to ensure new code is loaded
  7. 7. Verify the fix by testing that unaUTHORIZED users can no longer access quotes from private/hidden forums

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33398 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33398 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data