CVE-2026-8994 - WordPress Login with NEAR Plugin Authentication Bypass
The Login with NEAR plugin for WordPress is vulnerable to authentication bypass due to the `ajaxLoginWithNear()` function issuing valid authentication cookies based on a substring check of the `account` POST parameter, allowing unauthenticated attackers to log in as existing users or create new accounts.
The Login with NEAR plugin for WordPress, in versions up to and including 0.3.3, contains an authentication bypass vulnerability (CVE-2026-8994). The ajaxLoginWithNear() function, exposed to unauthenticated users via the wp_ajax_nopriv action, inadequately validates the account POST parameter. Specifically, it checks only for the presence of .near within the supplied account string. This flawed logic allows an attacker to forge a valid WordPress authentication cookie for any existing user whose email address matches the <account>@near.org pattern. Furthermore, if no such user exists, the plugin automatically creates a new WordPress account associated with the attacker-supplied account identifier. This vulnerability poses a significant risk, enabling attackers to gain unauthorized access and potentially escalate privileges to administrator level.
Attack Chain
- An unauthenticated attacker sends a POST request to
/wp-admin/admin-ajax.phpwith theactionparameter set tologin_with_near. - The attacker includes the
accountparameter in the POST request, setting its value to a string containing.nearand matching a target user’s email prefix (e.g.,admin.near). - The
ajaxLoginWithNear()function is triggered, processing the attacker’s craftedaccountvalue. - The function performs a substring check for
.nearwithin the suppliedaccountvalue but lacks proper cryptographic verification or nonce checks. - The plugin searches for a WordPress user with an email address matching
<account>@near.org(e.g.,admin.near@near.org). - If a matching user is found, a valid WordPress authentication cookie is issued for that user. If no user exists, a new user account is created using the attacker-supplied
accountidentifier. - The attacker receives the valid WordPress authentication cookie.
- The attacker uses the forged or newly created cookie to access the WordPress administration panel and other protected resources.
Impact
Successful exploitation of CVE-2026-8994 allows unauthenticated attackers to bypass authentication and gain unauthorized access to WordPress websites using the affected Login with NEAR plugin. Attackers can potentially log in as any existing user, including administrators, or create new unauthorized accounts. This can lead to complete site compromise, data theft, defacement, or other malicious activities. The severity of the impact depends on the privileges of the compromised user account.
Recommendation
- Apply the vendor-supplied patch or upgrade to a version of the Login with NEAR plugin greater than 0.3.3 to remediate CVE-2026-8994.
- Deploy the Sigma rule
Detect WordPress Login with NEAR Authentication Bypass Attemptto identify potential exploitation attempts targeting the vulnerableajaxLoginWithNearendpoint. - Monitor web server logs for POST requests to
/wp-admin/admin-ajax.phpwith theactionparameter set tologin_with_near(see ruleDetect WordPress Login with NEAR Authentication Bypass Attempt). - Review user accounts for any unauthorized accounts created with email addresses ending in
@near.org.
Detection coverage 2
Detect WordPress Login with NEAR Authentication Bypass Attempt
highDetects CVE-2026-8994 exploitation — attempts to exploit the authentication bypass in the Login with NEAR plugin by sending POST requests to the vulnerable ajaxLoginWithNear endpoint.
Detect WordPress Login with NEAR New Account Creation
mediumDetects WordPress user creation events for accounts ending in @near.org, which may indicate exploitation of CVE-2026-8994.
Detection queries are available on the platform. Get full rules →