WooCommerce - Social Login <= 2.8.7 - Unauthenticated Authentication Bypass via Forged Apple 'id_token' JWT
Strategic Overview
- Status
- Patched in 2.8.8
- Affected Plugin
- WooCommerce - Social Login
- Affected Version
<= 2.8.7- CVSS
- 9.8Critical
- Weakness type
- CWE-289 · Authentication Bypass by Alternate Name
- CVE
CVE-2026-8457
At a glance
CVE-2026-8457 is a critical-severity Authentication Bypass by Alternate Name vulnerability in the WooCommerce - Social Login WordPress plugin, affecting versions <= 2.8.7. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.8.8; sites on affected versions should update now. Disclosed August 2026, reported by Rafie Muhammad.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-289: Authentication Bypass by Alternate Name
Reaching this weakness in WooCommerce - Social Login <= 2.8.7 takes no account at all. Authentication bypass by alternate name means access checks are performed against one form of an identifier while the sensitive operation uses another, so a differently spelled value slips through.
Registering or supplying a variant spelling of a privileged account's identifier is enough to be treated as that account. For WooCommerce - Social Login the fix is 2.8.8: builds <= 2.8.7 are affected, anything from 2.8.8 onward is not.
Remediation
Update to version 2.8.8, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WooCommerce - Social Login 2.8.8 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WooCommerce - Social Login
- 9.8CVE-2024-7503: WooCommerce - Social Login Authentication Bypass
CVE-2024-7503 - 9.8CVE-2024-6636: WooCommerce… Unauthenticated Privilege Escalation
CVE-2024-6636 - 9.8CVE-2024-37502: WooCommerce Social Login <= 2.6.3 PHP Object Injection
CVE-2024-37502 - 9.8CVE-2024-5871: WooCommerce - Social Login PHP Object Injection
CVE-2024-5871 - 8.1CVE-2024-10114: Social Login - WordPress /… Authentication Bypass
CVE-2024-10114 - 7.3CVE-2024-6637: WooCommerce - Social Login Privilege Escalation
CVE-2024-6637 - 7.3CVE-2024-6635: WooCommerce - Social Login Authentication Bypass
CVE-2024-6635 - 6.5CVE-2024-5868: WooCommerce - Social Login Email Verification
CVE-2024-5868
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C