Wp Social Login and Register Social Counter <= 3.2.2 - Unauthenticated Authentication Bypass via Insufficient Email Verification in Social Login Callback
Strategic Overview
- Status
- Patched in 3.2.3
- Affected Plugin
- Wp Social Login and Register Social Counter
- Affected Version
<= 3.2.2- CVSS
- 8.1High
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-103898
At a glance
CVE-2026-103898 is a high-severity Improper Authentication vulnerability in the Wp Social Login and Register Social Counter WordPress plugin, affecting versions <= 3.2.2. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.2.3; sites on affected versions should update now. Disclosed October 2026, reported by Kumar Atul (Mandarin21).
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-287: Improper Authentication
Wp Social Login and Register Social Counter <= 3.2.2 carries this weakness at wp_set_auth_cookie(), and reaching it takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For Wp Social Login and Register Social Counter the fix is 3.2.3: builds <= 3.2.2 are affected, anything from 3.2.3 onward is not.
Remediation
Update to version 3.2.3, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Wp Social Login and Register Social Counter 3.2.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Wp Social Login and Register Social Counter
- 9.8CVE-2024-9501: Wp Social Login… Authentication Bypass
CVE-2024-9501 - 6.8CVE-2022-47160: Wp Social <= 1.9.0 Information Disclosure
CVE-2022-47160 - 6.5CVE-2024-1763: Wp Social Login… Unauthenticated Social Login/Share
CVE-2024-1763 - 6.4CVE-2026-97344: Wp Social Login and Register Social Counter Stored XSS
CVE-2026-97344 - 5.3CVE-2025-13620: Wp Social Login… Missing Authorization in Cache REST
CVE-2025-13620 - 4.3CVE-2025-1506: Wp Social Login and Register Social Counter CSRF
CVE-2025-1506
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C