dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-40571

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, `core/classes/Misc/ProfilePostReactionContext.php` only verifies that the wall post exists and does not enforce blocked/private-profile visibility. This means that authenticated low-privileged users can add reactions to private or blocking profile posts. Version 2.2.5 contains a patch.

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

In NamelessMC 2.2.4, the ProfilePostReactionContext.php class only validates that a wall post exists before allowing reactions, but fails to enforce visibility rules for private profiles and blocking relationships. This allows authenticated low-privileged users to react to profile posts they should not be able to access.

MitigationUpgrade to NamelessMC version 2.2.5 or later, which contains the patch implementing proper visibility and blocking checks before allowing profile post 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 NamelessMC installation and version
    Locate the version file in your NamelessMC installation directory (commonly version.php or similar in the root or core folder), or check the admin dashboard for the installed version number
    Affected if The installed version is 2.2.4 exactly
  2. Locate the affected source file
    Find ProfilePostReactionContext.php in the modules directory or source tree of your NamelessMC installation
    Affected if The file exists in the installation
  3. Verify the profile reaction feature is active
    Check if user profile wall/reaction functionality is enabled in the NamelessMC admin settings under modules or user profile settings
    Affected if Profile posting and reactions are enabled for users
  4. Inspect visibility enforcement in the affected file
    Open ProfilePostReactionContext.php and search for checks that enforce profile privacy settings or blocked user restrictions - look for missing logic around $user->hasViewPermission or similar visibility checks before allowing reactions
    Affected if The code only checks if the post exists but lacks checks for profile visibility (private profiles) or blocked user status before permitting reactions
  5. Confirm authenticated user access exists
    Verify that low-privilege authenticated users have access to the reaction endpoint and can submit reactions via the web interface or API
    Affected if Authenticated users can access the reaction functionality without proper visibility validation

You are affected if running NamelessMC version 2.2.4 with the ProfilePostReactionContext.php file present and profile reaction functionality enabled, where the code lacks visibility checks for private profiles or blocked users before allowing reactions.

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 or later, which contains the patch implementing proper visibility and blocking checks before allowing profile post reactions.

Recommended fix High confidence

NamelessMC version 2.2.5

  1. 1. Identify the current NamelessMC installation version (typically found in the admin dashboard or a version file)
  2. 2. Create a complete backup of the database and all website files
  3. 3. Download NamelessMC version 2.2.5 from the official GitHub repository or release page
  4. 4. Upload and extract the new version files to the server, replacing the existing installation
  5. 5. Run any database migrations if prompted during the upgrade process
  6. 6. Verify the upgrade was successful by checking the version number
  7. 7. Test that users cannot add reactions to private profile posts or posts from users who have blocked them

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-40571 — 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-40571 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