Skip to content
Tuesday, October 13, 2026AboutContactRSS
Vulnerabilities

WPCOM Member Plugin Critical Auth Bypass Lets Attackers Hijack Admin Accounts

A critical authentication bypass in the WPCOM Member WordPress plugin allows unauthenticated attackers to log in as any user, including administrators, through session forgery.

Updated with new details.
Illustration: A generic smartphone rests on a wooden desk, its screen displaying a blank, locked login interface.
AI-generated illustration: Threat Times

Key points

  • CVE-2026-104803 is rated CVSS 9.8 Critical due to complete authentication bypass.
  • The flaw affects all WPCOM Member plugin versions up to and including 1.7.27.
  • Attackers can hijack accounts if they know or can discover the victim's social provider ID.

The WPCOM Member plugin for WordPress contains a critical authentication bypass vulnerability that allows unauthenticated attackers to log in as any user, including site administrators. The flaw, tracked as CVE-2026-104803, affects all plugin versions up to and including 1.7.27 and has been assigned a CVSS score of 9.8, indicating a severe risk to WordPress installations using this specific social login tool.

At a glance

CVE
CVE-2026-104803
Product
whyun WPCOM Member
CVSS
9.8 Critical
Weakness
improper authentication
Exploited
No known exploitation

According to the National Vulnerability Database record, the vulnerability stems from missing security controls in the plugin's social-login callback handler. The handler is registered on the `init` hook and processes `uuid` and `code` parameters without performing nonce validation, OAuth state verification, or per-visitor namespace isolation in the session store. This lack of validation enables an attacker to manipulate session data through crafted requests.

Technical Context and Exploitation

The exploitation process involves two distinct GET requests issued by an unauthenticated attacker. First, the attacker sends a request that writes an attacker-named and attacker-valued entry into the global session namespace. This is achieved by bypassing the per-visitor prefix mechanism through the use of an underscore character. This step allows the attacker to inject arbitrary data into the session store without proper authentication.

The second request triggers the `weapp_new_user()` function, which reads the forged session entry. This function resolves the attacker-supplied `openid` value to a bound WordPress account. Once this resolution occurs, the `wp_set_auth_cookie()` function establishes a fully authenticated session for the attacker. This sequence effectively allows the attacker to assume the identity of any WordPress user whose bound social provider identifier is known or can be discovered through enumeration.

Affected Systems and Requirements

The vulnerability is present in the WPCOM Member plugin developed by whyun. It affects all versions of the software up to and including version 1.7.27. Any WordPress site that has installed this plugin within that version range is potentially vulnerable, provided that the site has configured at least one social provider. The configuration of a social provider is a necessary condition because it activates the vulnerable callback handler that processes the social login flow.

Successful exploitation requires that the attacker knows or can enumerate the victim account's bound `openid` or `unionid`. These identifiers link the WordPress user account to the external social provider. If these identifiers are not discoverable, the attack vector is significantly hindered. However, if the identifiers are exposed through public profiles or other means, the risk of account takeover increases substantially for administrators and other users.

What should you do?

Site administrators should immediately audit their WordPress installations to determine if the WPCOM Member plugin is installed and check its current version. If the plugin version is 1.7.27 or older, the site is vulnerable to this critical authentication bypass. Administrators should review access logs for unusual login patterns or unexpected session creations, particularly those originating from unauthenticated sources. Monitoring for requests containing `uuid` and `code` parameters in the callback handler can help detect active exploitation attempts.

What to do and how to stay safe: WPCOM Member

  • Verify if the WPCOM Member plugin is installed and check if the version is 1.7.27 or older.
  • Monitor server logs for unauthenticated GET requests targeting the social-login callback handler.
  • Ensure that social provider identifiers like openid or unionid are not publicly exposed.
  • Once the vendor provides an update, apply the patch immediately to mitigate the risk.

Step-by-step guide: Risk Based Vulnerability Management: Prioritize Fixes by Actual Threat

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is the CVSS score for CVE-2026-104803?

The CVSS score for CVE-2026-104803 is 9.8, which is rated as Critical.

Which versions of WPCOM Member are affected?

All versions of the WPCOM Member plugin up to and including 1.7.27 are affected.

Can an attacker log in as an administrator?

Yes, an attacker can log in as any WordPress user, including administrators, if they know the bound social provider identifier.

Sources

  1. CVE Program
WPCOM MemberWordPressCVE-2026-104803whyunAuthentication Bypass
Related articles