Plugins · wp-social · data as of 2026-11-04
Is Wp Social Login and Register Social Counter safe? Known vulnerabilities and latest version
- Latest version
- 3.2.3
- Last updated
- 2026-10-18
- Active installs
- 70,000+
- Known issues on record
- 7
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
Wp social lets you add social login, social counter, and social share buttons of different styles to your WordPress website. — by Roxnor
What to do
- Update to the latest version (3.2.3). Anything older than 3.2.3 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get wp-social --field=version shows what you run; wp plugin update wp-social updates it.
Check your version
Known vulnerabilities
7 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
high 8.1 CVE-2026-103898 · published 2026-10-31
Authentication bypass in Wp Social Login and Register Social Counter (3.2.2 and older)
- Affected
- 3.2.2 and older
- Fixed in
- 3.2.3 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-103898Wordfence advisoryCode change (fix)Plugin source
medium 6.4 CVE-2026-97344 · published 2026-10-03
Stored cross-site scripting (XSS) in Wp Social Login and Register Social Counter (3.2.1 and older)
- Affected
- 3.2.1 and older
- Fixed in
- 3.2.2 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Wp Social Login and Register Social Counter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Avatar Alt Attribute via Arbitrary User Meta Write in all versions up to, and including, 3.2.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the attacker to chain two steps: invoking the nonce-only dismiss_ajax_call endpoint (nonce accessible to Subscribers via any wp-admin page) to set the xs_social_profile_image meta flag on their own account, which activates the unescaped img output branch in xs_social_get_avatar, and then setting their display name to a script payload that core's ENT_NOQUOTES handling preserves unescaped.
NVD CVE-2026-97344Wordfence advisoryCode change (fix)Plugin source
medium 5.3 CVE-2025-13620 · published 2025-12-05
Missing authorization check in Wp Social Login and Register Social Counter (3.1.3 and older)
- Affected
- 3.1.3 and older
- Fixed in
- 3.1.4 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Wp Social Login and Register Social Counter plugin for WordPress is vulnerable to missing authorization in versions up to, and including, 3.1.3. This is due to the REST routes wslu/v1/check_cache/{type}, wslu/v1/save_cache/{type}, and wslu/v1/settings/clear_counter_cache being registered with permission_callback set to __return_true and lacking capability or nonce validation in their handlers. This makes it possible for unauthenticated attackers to clear or overwrite the social counter cache via crafted REST requests.
NVD CVE-2025-13620Wordfence advisoryCode change (fix)research.cleantalk.org
medium 4.3 CVE-2025-1506 · published 2025-02-28
Cross-site request forgery (CSRF) in Wp Social Login and Register Social Counter (3.1.0 and older)
- Affected
- 3.1.0 and older
- Fixed in
- 3.1.1 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Wp Social Login and Register Social Counter plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.1.0. This is due to missing or incorrect nonce validation on the counter_access_key_setup() function. This makes it possible for unauthenticated attackers to update social login provider settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
NVD CVE-2025-1506Wordfence advisoryCode change (fix)Plugin source
critical 9.8 CVE-2024-9501 · published 2024-10-26
Authentication bypass in Wp Social Login and Register Social Counter (3.0.7 and older)
- Affected
- 3.0.7 and older
- Fixed in
- 3.0.8 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Wp Social Login and Register Social Counter plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 3.0.7. This is due to insufficient verification on the user being returned by the social login token. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the email and the user does not have an already-existing account for the service returning the token.
NVD CVE-2024-9501Wordfence advisoryCode change (fix)Plugin source
medium 5.3 CVE-2024-1763 · published 2024-03-13
Missing authorization check in Wp Social Login and Register Social Counter (3.0.0 and older)
- Affected
- 3.0.0 and older
- Fixed in
- 3.0.2 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
The Wp Social Login and Register Social Counter plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the /wp_social/v1/ REST API endpoint in all versions up to, and including, 3.0.0. This makes it possible for unauthenticated attackers to enable and disable certain providers for the social share and login features.
medium 6.5 CVE-2022-47160 · published 2024-01-19
Information disclosure in Wp Social Login and Register Social Counter (1.9.0 and older)
- Affected
- 1.9.0 and older
- Fixed in
- 2.0
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Wpmet Wp Social Login and Register Social Counter.This issue affects Wp Social Login and Register Social Counter: from n/a through 1.9.0.
Recent activity
- 2026-10-18 — latest release on wordpress.org (3.2.3).
- 2026-10-31 — Authentication bypass disclosed (CVE-2026-103898), fixed in 3.2.3.
- 2026-10-03 — Stored cross-site scripting (XSS) disclosed (CVE-2026-97344), fixed in 3.2.2.
- 2025-12-05 — Missing authorization check disclosed (CVE-2025-13620), fixed in 3.1.4.
Get an email when Wp Social Login and Register Social Counter has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Wp Social Login and Register Social Counter (wp-social) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by Roxnor (10 tracked)
Types found in this plugin: Authentication bypass (2) · Missing authorization (2) · Cross-site scripting (XSS) (1) · Cross-site request forgery (CSRF) (1) · Sensitive data exposure (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/wp-social (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/wp-social"><img src="https://laskyr.com/plugins/wp-social/badge.svg" alt="Wp Social Login and Register Social Counter vulnerability status"></a>