dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-8994

HIGH · 8.1 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
The Login with NEAR plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 0.3.3. The `ajaxLoginWithNear()` function — registered as a `wp_ajax_nopriv` action and therefore reachable by unauthenticated users — accepts an attacker-supplied `account` POST parameter and issues a valid WordPress authentication cookie based solely on a substring check for `.near`, with no nonce verification, cryptographic signature validation, challenge-response exchange, or any proof that the requester controls the corresponding NEAR wallet. This makes it possible for unauthenticated attackers to log in as any existing WordPress user, including administrators, whose email address matches the deterministic `<account>@near.org` pattern derived from the supplied `account` value. If no matching user exists, the handler automatically creates and authenticates a new WordPress account for the attacker-controlled identifier, providing a further avenue for unauthorized account creation.

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 Login with NEAR plugin for WordPress (versions up to 0.3.3) contains an authentication bypass in its `ajaxLoginWithNear()` function. This function, accessible to unauthenticated users via wp_ajax_nopriv, accepts an attacker-supplied `account` POST parameter and issues valid WordPress authentication cookies based solely on a substring check for '.near', without any cryptographic signature validation, nonce verification, or proof of wallet ownership. Attackers can log in as any existing user whose email follows the `<account>@near.org` pattern, or have the plugin auto-create a new attacker-controlled account.

MitigationImmediately disable or remove the Login with NEAR plugin until a patched version with proper cryptographic signature verification is available. Audit WordPress user accounts for any unauthorized entries created via this vulnerability.

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

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

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 Login with NEAR plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins and locate 'Login with NEAR' in the list. The version number is displayed below the plugin name.
    Affected if The installed version is 0.3.3 or lower.
  2. Confirm plugin is active
    In the same plugins list, verify the 'Login with NEAR' plugin has an 'Active' status indicator.
    Affected if The plugin is active and the version is 0.3.3 or lower.
  3. Check for suspicious near.org user accounts
    Go to WordPress admin > Users > All Users. Review the email addresses for any accounts ending in @near.org that you did not intentionally create. Note that usernames may appear as wallet addresses.
    Affected if Any user accounts with @near.org email addresses exist and were not deliberately provisioned by an administrator.
  4. Audit user creation dates
    In the users list, check the 'Registered' column timestamp. Look for accounts created around the time the plugin was installed or activated, especially if they have near.org emails.
    Affected if New user accounts appeared in the database after the Login with NEAR plugin was installed, particularly with near.org email addresses.

You are affected if the Login with NEAR plugin version 0.3.3 or lower is active on your WordPress site, or if unauthorized @near.org user accounts exist in your database.

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

Immediately disable or remove the Login with NEAR plugin until a patched version with proper cryptographic signature verification is available. Audit WordPress user accounts for any unauthorized entries created via this vulnerability.

Recommended fix High confidence

Login with NEAR plugin version 0.3.4

  1. Update the Login with NEAR plugin to version 0.3.4 or later
  2. After updating, verify that the wp_ajax_nopriv_ajaxLoginWithNear action is no longer accessible to unauthenticated users or has been properly secured with cryptographic signature validation
  3. Audit existing WordPress user accounts for any unauthorized accounts created with @near.org email patterns
  4. Consider resetting passwords for administrator accounts as a precautionary measure

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