dbcve.org
CWE-302Weakness · CWE-302

CVE-2026-34460

MEDIUM · 5.4 CVSS v3.1 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 →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 versions 2.2.4 and prior, the OAuth callback handling does not validate the state parameter server-side before exchanging the authorization code. This allows an attacker to capture a valid OAuth callback URL for their own account and cause a victim's browser to navigate to it, resulting in the victim's session being authenticated as the attacker-linked account (OAuth login CSRF / session swapping). This is patched in version 2.2.5.

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 versions 2.2.4 and prior fail to validate the OAuth state parameter server-side during callback handling. An attacker can capture a valid OAuth callback URL for their own account and trick a victim into visiting it, causing the victim's session to become authenticated as the attacker's linked account (OAuth login CSRF / session swapping). Version 2.2.5 patches this by implementing proper state parameter validation.

MitigationUpgrade to NamelessMC version 2.2.5 or later which includes server-side state parameter validation to prevent OAuth callback manipulation.

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
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

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. Determine installed NamelessMC version
    Log into the NamelessMC admin dashboard and navigate to Configuration > General, or check the file core/version.php for the version number
    Affected if Version is 2.2.4 or any version prior to 2.2.5
  2. Verify OAuth integration is enabled
    In the admin dashboard, go to Configuration > OAuth or Settings > Sign-in Methods and check if any OAuth provider (Discord, Google, etc.) is configured and enabled
    Affected if OAuth integration is configured with at least one provider
  3. Check for state parameter validation in OAuth callback handler
    Inspect the OAuth callback endpoint code in the NamelessMC installation (typically in modules/OAuth or similar path) to verify if server-side state parameter validation exists before exchanging the authorization code
    Affected if No server-side state validation is present in the OAuth callback handling code

If the installed NamelessMC version is 2.2.4 or prior and OAuth is enabled with at least one provider configured, the environment is vulnerable to the session swapping attack described in CVE-2026-34460.

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 includes server-side state parameter validation to prevent OAuth callback manipulation.

Recommended fix High confidence

2.2.5

  1. 1. Back up your existing NamelessMC installation and database before proceeding.
  2. 2. Download NamelessMC version 2.2.5 from the official GitHub repository (github.com/NamelessMC/Nameless) or your distribution method.
  3. 3. Replace the existing NamelessMC files with the new version 2.2.5 files, preserving your configuration and custom assets.
  4. 4. Run any database migrations included in the 2.2.5 release.
  5. 5. Verify the OAuth login flow now correctly validates the state parameter server-side before exchanging authorization codes.
  6. 6. Test OAuth login functionality to confirm the CSRF protection is working properly.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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