WooCommerce Social Login accepts forged Apple identity tokens
WooCommerce - Social Login through 2.8.7 decodes the Apple id_token payload without verifying its JWT signature against Apple's keys or validating the issuer, audience or expiry. The nonce needed to enter the Apple login flow is localized into the public login page, so an unauthenticated visitor can submit a forged token naming any existing user's email address. The plugin resolves that email without excluding privileged roles and immediately creates a WordPress session, allowing Administrator takeover. The CNA record does not disclose the handler, endpoint, action or request parameter that carries the token.
- Component
- WooCommerce - Social Login
- Plugin slug
woocommerce-social-login- Affected
- <= 2.8.7
- Safe version
2.8.8- Published
- Aug 02, 2026
This CVE was published Aug 02, 2026 and is one of 9 known issues for this plugin.
Update, patch or deactivate.
Update WooCommerce - Social Login to 2.8.8 or later; the vendor changelog identifies 2.8.8 as improving Apple Sign-In ID-token validation and verification. Invalidate active sessions, reset privileged credentials, review Apple social-login activity and investigate Administrator actions on sites that exposed the vulnerable flow.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H