CVE-2026-103898: Wp Social Login and Register Social Counter · Improper Authentication
Affects Wp Social Login and Register Social CounterSource CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 31 Oct 2026, 08:20 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 8.1 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 31 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| roxnorWp Social Login and Register Social Counter | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor's advisory for updates. Until a fix is available, consider disabling the Wp Social Login and Register Social Counter plugin or restricting access to the vulnerable REST endpoint. Avoid relying on social login providers that do not properly verify email addresses. Implement additional access controls or multi-factor authentication to reduce risk.
Description
The Wp Social Login and Register Social Counter WordPress plugin up to version 3.2.2 contains an authentication bypass vulnerability. This flaw allows unauthenticated attackers to gain authenticated sessions as any existing WordPress user, including administrators, by exploiting improper verification of OAuth provider email addresses. The vulnerability arises because the plugin's REST callback accepts any email returned by Facebook or Twitter OAuth providers without proper verification, enabling attackers controlling an OAuth account with a matching email to bypass password checks.
References
- wordfence.com/threat-intel/vulnerabilities/id/e961d3db-da5e-4bde-ae7e-04e6ba3ebef4?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-social/tags/3.2.1/inc/admin-create-user.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-social/tags/3.2.1/inc/admin-create-user.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-social/tags/3.2.1/inc/admin-create-user.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-social/tags/3.2.1/inc/admin-rest-api.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-social/tags/3.2.1/lib/composer/vendor/hybridauth/hybridauth/src/Provider/Facebook.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-social/tags/3.2.1/lib/composer/vendor/hybridauth/hybridauth/src/Provider/Twitter.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3752566%40wp-social&new=3752566%40wp-social (opens in a new tab)