Skip to main content
VulnerabilityPublished

CVE-2026-103898: Wp Social Login and Register Social Counter · Improper Authentication

Affects Wp Social Login and Register Social CounterSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.18.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
roxnorWp Social Login and Register Social CounterAffected
  • <=3.2.2
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

Community reviews

Loading reviews…