---
id: "CVE-2026-103898"
kind: "vulnerability"
aliases: ["CVE-2026-103898"]
title: "WordPress social login plugin lets attackers log in as any user"
severity: "high"
cvss: 8.1
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "wp-social", "fixed": ["3.2.3"], "affected": "<= 3.2.2", "ecosystem": "wordpress"}]
ecosystems: []
tags: ["package", "self-hosted", "wordpress", "wordpress-plugin"]
not_affected_if: ["plugin-not-installed", "social-login-not-configured"]
published_at: "2026-10-31T08:16:47+00:00"
first_seen_at: "2026-10-31T08:34:27+00:00"
updated_at: "2026-10-31T08:36:16+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-103898", "first_seen_at": "2026-10-31T08:34:27+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-31T08:36:16+00:00"}]
---

# WordPress social login plugin lets attackers log in as any user

The Wp Social Login and Register Social Counter WordPress plugin up to version 3.2.2 trusts the email address returned by a Facebook or Twitter login without verifying it. An attacker who controls an OAuth account with the same email as a WordPress user, including an Administrator, gets a fully authenticated session as that user.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- wordpress:wp-social affected <= 3.2.2 fixed 3.2.3

## How to check

In WordPress admin > Plugins, find 'Wp Social Login and Register Social Counter' (folder wp-social); versions <= 3.2.2 are affected. Exposure needs Facebook or Twitter login configured under the Wp Social login settings. Also check whether /wp-json/wslu-social-login/type/facebook/ exists on the site.

## Fix

Update the Wp Social Login and Register Social Counter plugin (slug wp-social) to 3.2.3 or later.

## Timeline

- 2026-10-31T08:34:27+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-103898
- 2026-10-31T08:36:16+00:00 analyst — Fix 3.2.3 per wordpress.org listing (current version 3.2.3) and PluginCheck (patched in 3.2.3); I could not read the plugin changelog or Wordfence advisory, so the 3.2.3 fix claim rests on those, not a maintainer changelog entry. No exploitation or PoC found. Nothing marked verified.

## Documents

- [fix] Wp Social plugin page (current version 3.2.3) https://wordpress.org/plugins/wp-social/advanced/
- [mentions] PluginCheck: Wp Social security history (patched in 3.2.3) https://plugincheck.io/plugin/wp-social

## From the sources

The Wp Social Login and Register Social Counter plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 3.2.2. This is due to the social login REST callback registered at `/wp-json/wslu-social-login/type/{provider}/` with `permission_callback => __return_true` locating an existing WordPress account solely by the email string returned from the OAuth provider and calling `wp_set_auth_cookie()` without a password check, while the only verification guard — `!empty($getProfile->emailVerified)` in `inc/admin-create-user.php` — is a no-op for the bundled Hybridauth Facebook and Twitter adapters, both of which assign the raw email string rather than a boolean verified flag to `emailVerified`. This makes it possible for unauthenticated attackers to obtain a fully authenticated session as any existing WordPress user, including Administrators, whose registered email address can be presented through a configured Facebook or Twitter login on the target site. Exploitation requires only that the attacker control an OAuth account whose provider-returned email matches the target account's registered WordPress email address; no local credentials, nonce, or prior foothold is needed.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_