Read the docs

Authentication bypass in WPCOM Member plugin social-login callback

Priority MEDIUM 49CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-287.

Summary

The WPCOM Member plugin for WordPress through 1.7.27 has an authentication bypass in its social-login callback (CWE-287). The handler performs no nonce or OAuth state checks and does not isolate session data per visitor, so a forged session entry can be accepted as a social login. An unauthenticated remote attacker can log in as any WordPress user, including administrators, whose bound social provider identifier is known or discoverable, provided the site has at least one social provider configured.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

The WPCOM Member plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.7.27 via the `uuid` and `code` parameters of the social-login callback handler registered on the `init` hook. The vulnerability exists because the `login` function's social-login flow performs no nonce validation, no OAuth state verification, and no per-visitor namespace isolation in the session store, allowing an unauthenticated attacker to issue a crafted GET request that writes an attacker-named, attacker-valued entry into the global session namespace (bypassing the per-visitor prefix by prepending an underscore), then issue a second GET request triggering `weapp_new_user()` to read that forged entry and resolve the attacker-supplied `openid` value to a bound WordPress account before `wp_set_auth_cookie()` establishes a fully authenticated session. This makes it possible for unauthenticated attackers to log in as any WordPress user — including administrators — whose bound social provider identifier (openid/unionid) is known or discoverable. Successful exploitation requires that the target site has at least one social provider configured (which activates the vulnerable handler) and that the attacker knows or can enumerate the victim account's bound openid or unionid.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00449 39th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
whyunWPCOM Memberup to 1.7.27—No fix listedCNA
  • WPCOM Member Vendorwhyun Affected up to 1.7.27 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for WPCOM Member.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Timeline

  1. 2026-10-10 Threatist record created from CVE-2026-104803
  2. 2026-10-10 Alias added: GHSA-gj32-ffvm-frj6
  3. 2026-10-11 CISA SSVC decision points changed

References

  • TI-2025-01268 WPCOM Member <= 1.7.5 - Authentication Bypass via 'user_phone' CVSS 3.1CRITICAL 9.8
  • TI-2025-10929 WPCOM Member <= 1.7.14 - Authenticated (Contributor+) Local File Inclusion via Shortcode CVSS 3.1HIGH 8.8
  • TI-2025-12793 WPCOM Member <= 1.7.16 - Authentication Bypass via Weak OTP CVSS 3.1HIGH 8.1

Sources