Wp Social Login and Register Social Counter <= 3.2.2 - Unauthenticated Authentication Bypass via Insufficient Email Verification in Social…
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Wp Social Login and Register Social Counter WordPress plugin, in all versions up to and including 3.2.2, lets an unauthenticated attacker log in as any existing site user, including administrators, by presenting a social login account (via Facebook or Twitter) that uses the same email address as the target account. This gives the attacker full access to the affected WordPress site and its administrative controls.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- roxnor Wp Social Login and Register Social Counter
through 3.2.2
References 8
plugins.trac.wordpress.org
- browser/wp-social/tags/3.2.1/inc/admin-create-user.php#L229
- browser/wp-social/tags/3.2.1/inc/admin-create-user.php#L512
- browser/wp-social/tags/3.2.1/inc/admin-create-user.php#L172
- browser/wp-social/tags/3.2.1/inc/admin-rest-api.php#L46
- browser/wp-social/tags/3.2.1/lib/composer/vendor/hybridauth/hybridauth/src/Provider/Facebook.php#L205
- browser/wp-social/tags/3.2.1/lib/composer/vendor/hybridauth/hybridauth/src/Provider/Twitter.php#L102
- changeset?reponame=&old=3752566%40wp-social&new=3752566%40wp-social