Radar sectionsDatabase
Check my site
WordPress plugin

WooCommerce — Social Login <= 2.8.7 - Unauthenticated Authentication Bypass via Forged Apple 'id_token' JWT

CVE-2026-8457Published · Updated

Action summary

Affected: ≤2.8.7Update to 2.8.8 or newer

All remediation steps
Severity
Critical9.8
CVSS
9.8
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:H Confidentiality
High
I:H Integrity
High
A:H Availability
High
Weakness
CWE-289 Authentication Bypass by Alternate Name
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

WooCommerce - Social Login woo-social-login

  1. Affected≤ 2.8.7
  2. Patched in2.8.8

Update to 2.8.8 or newer.

You are affected if you run ≤ 2.8.7. Version 2.8.8 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under WooCommerce - Social Login.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.8.8, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch WooCommerce - Social Login to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Rafie Muhammad.

The WooCommerce - Social Login plugin for WordPress is vulnerable to Authentication Bypass in all versions up to and including 2.8.7. This is due to the plugin's Apple login handler accepting the Apple id_token and decoding only its base64 payload without verifying the JWT signature against Apple's public keys or validating the issuer, audience, or expiry claims, combined with the security nonce required to invoke the login flow being publicly exposed to unauthenticated users via a localized JavaScript object on the login page. This makes it possible for unauthenticated attackers to log in as any existing WordPress user — including administrators — by supplying a forged id_token whose payload contains the target user's email address, as that email is used without any role exclusion to resolve a WordPress account and immediately issue an authenticated session for it.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in WooCommerce - Social Login

All 10
More vulnerabilities in WooCommerce - Social Login
SeverityVulnerabilityCVEPublished
Medium4.3Cross-Site Request Forgery
≤2.8.2Update to 2.8.3
CVE-2025-39472
High8.1WordPress / WooCommerce Plugin <= 2.7.7 - Authentication Bypass via WordPress.com OAuth provider
≤2.7.7Update to 2.7.8
CVE-2024-10114
Critical9.8Social Login <= 2.7.5 - Authentication Bypass to Account Takeover
≤2.7.5Update to 2.7.6
CVE-2024-7503
Critical9.8Social Login <= 2.7.3 - Missing Authorization to Unauthenticated Privilege Escalation
≤2.7.3Update to 2.7.4
CVE-2024-6636
High7.3Social Login <= 2.7.3 - Unauthenticated Privilege Escalation via One-Time Password
≤2.7.3Update to 2.7.4
CVE-2024-6637

Timeline

  1. CVE published

    Severity critical, CVSS 9.8

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?