dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-40314

MEDIUM · 6.9 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 →
78/100
Remediation priority · High
Remotely reachable No privileges 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,`core/classes/Misc/ProfilePostReactionContext.php` only verifies that the wall post exists and does not enforce blocked/private-profile visibility. `modules/Core/queries/reactions.php` allows unauthenticated GET requests for reaction details. This means that unauthenticated visitors can read reaction participants and timestamps for private profile posts and uthenticated low-privileged users can add reactions to private or blocking profile posts. 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

NamelessMC 2.2.4 has broken access control in ProfilePostReactionContext.php which verifies wall post existence but fails to enforce blocked/private-profile visibility rules. Additionally, reactions.php permits unauthenticated GET requests for reaction details. This allows unauthenticated visitors to read reaction participants and timestamps on private profile posts, and allows authenticated low-privilege users to react to posts on private or blocking profiles.

MitigationUpgrade to NamelessMC version 2.2.5 which contains the fix for proper authorization and visibility enforcement.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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 NamelessMC installation and version
    Locate the NamelessMC installation directory and check the version file (typically version.php or similar in the root/includes directory). Compare the installed version number to 2.2.4.
    Affected if The installed version is exactly 2.2.4.
  2. Verify presence of vulnerable files
    Confirm that ProfilePostReactionContext.php and reactions.php exist in the NamelessMC installation, typically under the modules or core directories.
    Affected if Both ProfilePostReactionContext.php and reactions.php exist in the NamelessMC installation.
  3. Check for private or blocking profile configurations
    Review the NamelessMC admin panel or database to identify if any user profiles have been set to private or if blocking functionality is enabled.
    Affected if Private profiles exist or the blocking feature is enabled in the system.
  4. Test unauthenticated access to reactions endpoint
    Send a GET request to the reactions.php endpoint without authentication credentials and observe whether the server returns reaction data for profile posts.
    Affected if The server responds with reaction participant data or timestamps without requiring authentication.

A user is affected if running NamelessMC version 2.2.4 with the vulnerable files present and private profiles or blocking features enabled, combined with the reactions.php endpoint accepting unauthenticated requests.

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 contains the fix for proper authorization and visibility enforcement.

Recommended fix High confidence

2.2.5

  1. Backup the current NamelessMC installation and database
  2. Download NamelessMC version 2.2.5 from the official source
  3. Replace the existing installation files with the 2.2.5 files
  4. Run any included database migrations if required
  5. Verify the upgrade was successful by testing the reaction functionality

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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