dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-35443

MEDIUM · 5.3 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 →
59/100
Remediation priority · Elevated
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/classes/ForumPostReactionContext.php` only verifies that the caller can view the forum, but it does not re-enforce topic-level `view_other_topics` authorization. As a result, in forums where users may enter the forum but may only view their own topics, reactions can still be read and modified on other users' topics. 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

The forum reaction handler in ForumPostReactionContext.php only validates forum-level view permissions but fails to re-enforce topic-level 'view_other_topics' authorization. This allows users who can access a forum but should only view their own topics to still read and modify reactions on other users' topics, constituting an authorization bypass.

MitigationUpgrade NamelessMC to version 2.2.5 or later which includes the proper topic-level authorization check for forum reactions.

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:L/VI:L/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 installed NamelessMC version
    Locate the version file or admin dashboard version display (commonly in /core/ or the admin panel) to confirm the running version is 2.2.4
    Affected if The installed version is exactly 2.2.4 (earlier versions or 2.2.5+ are not affected)
  2. Locate ForumPostReactionContext.php
    Find the file ForumPostReactionContext.php within the NamelessMC installation, typically in the modules/forum directory structure
    Affected if The file exists in the installation and originates from version 2.2.4
  3. Verify missing view_other_topics permission check
    Open ForumPostReactionContext.php and search for code that checks forum-level view permissions (e.g., checkPermissions or view permission) but lacks a corresponding check for the topic-level view_other_topics permission
    Affected if The file contains only forum-level permission checks without enforcing the topic-level view_other_topics permission
  4. Confirm restricted forum topic configuration
    Review the forum configuration in the NamelessMC admin panel to identify forums with restricted access settings where certain user groups should be denied topic visibility
    Affected if Restricted forums exist where view_other_topics permissions would limit access to certain topics
  5. Test cross-user reaction visibility
    As a user in a restricted group, attempt to view or modify reactions on topics in forums where they lack view_other_topics permission
    Affected if Users can read or modify reactions on topics they should not have access to based on topic-level permissions

A user is affected if running NamelessMC 2.2.4 with ForumPostReactionContext.php that lacks topic-level view_other_topics permission enforcement, and has restricted forums configured where this permission boundary matters.

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 NamelessMC to version 2.2.5 or later which includes the proper topic-level authorization check for forum reactions.

Recommended fix High confidence

2.2.5

  1. Upgrade NamelessMC from version 2.2.4 to version 2.2.5

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35443 — 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-35443 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