Skip to main content
Vulnerability Database/CVE-2026-104803

CVE-2026-104803: WPCOM Member Auth Bypass Vulnerability

CVE-2026-104803 is an authentication bypass flaw in WPCOM Member plugin for WordPress that lets attackers log in as any user by exploiting flawed social-login validation. This article covers technical details, affected versions, impact, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-104803 Overview

CVE-2026-104803 is an authentication bypass vulnerability in the WPCOM Member plugin for WordPress affecting all versions up to and including 1.7.27. The flaw resides in the social-login callback handler registered on the init hook, which fails to perform nonce validation, OAuth state verification, or per-visitor namespace isolation in the session store. An unauthenticated attacker can craft two sequential GET requests to inject a forged session entry and then trigger weapp_new_user() to resolve an attacker-supplied openid to a bound WordPress account. Successful exploitation establishes a fully authenticated session as any user, including administrators.

Critical Impact

Unauthenticated attackers who know or can enumerate a victim's bound openid or unionid can log in as any WordPress user, including administrators, on sites with at least one social provider configured.

Affected Products

  • WPCOM Member plugin for WordPress — all versions up to and including 1.7.27
  • WordPress sites with at least one social provider configured in the plugin
  • Any WordPress installation where the vulnerable init hook handler is active

Discovery Timeline

  • 2026-10-10 - CVE-2026-104803 published to NVD
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-104803

Vulnerability Analysis

The vulnerability is categorized as Authentication Bypass [CWE-287] and arises from unsafe handling of the uuid and code parameters in the social-login callback. The plugin's login function processes these parameters without validating request authenticity. Because the session store lacks per-visitor isolation, an attacker can write arbitrary entries into a globally reachable namespace. The handler then trusts those entries during subsequent account resolution and issues wp_set_auth_cookie() for the bound account. This grants persistent, full-session access to the targeted WordPress user.

Root Cause

Three compounding defects produce the bypass. First, the social-login flow performs no nonce validation and no OAuth state verification, so request origin cannot be trusted. Second, the session storage class does not enforce a per-visitor prefix integrity check, allowing a client to bypass namespace isolation by prepending an underscore to a key. Third, weapp_new_user() reads the forged session entry and resolves the attacker-supplied openid directly against bound WordPress accounts without re-authenticating the provider.

Attack Vector

The attacker sends an unauthenticated GET request to the social-login endpoint, supplying crafted uuid and code values that write an attacker-controlled key and value into the global session namespace. A second GET request triggers weapp_new_user(), which consumes the forged entry, resolves the chosen openid or unionid to the victim's WordPress account, and invokes wp_set_auth_cookie(). Exploitation requires knowledge or enumeration of the target account's bound social identifier. See the Wordfence CVE Vulnerability Analysis and the WordPress Plugin Social Login Code for implementation specifics.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-104803

Indicators of Compromise

  • Repeated unauthenticated GET requests to the WPCOM Member social-login callback with unusual uuid and code parameter values.
  • WordPress authentication cookies issued without a corresponding successful OAuth round trip to the external social provider.
  • Administrator or privileged user logins from IP addresses or user agents that have no prior login history.
  • New sessions established immediately after two sequential init-hook callback requests from the same client.

Detection Strategies

  • Correlate wp_set_auth_cookie events with the presence of a legitimate upstream OAuth exchange to the configured social provider.
  • Monitor web access logs for sequential GET requests to the social-login endpoint from the same source within a short time window.
  • Alert on session store writes where the key contains an underscore-prefixed value that circumvents the expected per-visitor prefix.

Monitoring Recommendations

  • Enable verbose authentication logging for WordPress and forward events to a centralized log platform for correlation.
  • Track administrator session creation and surface any session whose creation path did not include provider token validation.
  • Baseline normal social-login request patterns and alert on bursts of callback traffic that do not resolve to real user signups.

How to Mitigate CVE-2026-104803

Immediate Actions Required

  • Update the WPCOM Member plugin to a version later than 1.7.27 as soon as a patched release is published by the vendor.
  • Deactivate the WPCOM Member plugin on any site where a patched version is not yet available.
  • Rotate credentials and force reauthentication for administrator and privileged WordPress accounts.
  • Audit recent authentication events for unexpected logins and revoke suspicious sessions.

Patch Information

No fixed version is identified in the available NVD data at the time of publication. Monitor the WordPress Plugin Social Login Code repository and the Wordfence CVE Vulnerability Analysis for updates and apply the vendor-supplied patch when released.

Workarounds

  • Disable all configured social providers in the WPCOM Member plugin to deactivate the vulnerable init hook handler.
  • Restrict access to the social-login callback endpoint using a web application firewall rule until a patch is applied.
  • Treat openid and unionid values as sensitive and avoid exposing them in public user profiles, APIs, or site exports.
bash
# Configuration example
# Temporary WAF rule concept to block the vulnerable callback until patched
# Replace path with the actual callback route used by the WPCOM Member plugin
SecRule REQUEST_METHOD "@streq GET" \
  "chain,id:1026104803,phase:1,deny,status:403,log,msg:'Block WPCOM Member social-login callback (CVE-2026-104803)'"
SecRule REQUEST_URI "@contains /?wpcom_social_login=" \
  "chain"
SecRule ARGS_NAMES "@rx ^(uuid|code)$"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.