CVE-2026-8457 WPWeb CVE debrief

Who should care

Defenders responsible for WordPress installations with the WooCommerce - Social Login plugin should assess exposure and prioritize patching to prevent authentication bypass attacks.

Why it matters

The WooCommerce - Social Login plugin for WordPress is vulnerable to Authentication Bypass, allowing unauthenticated attackers to log in as any existing WordPress user, including administrators. Defenders should prioritize verifying the plugin version and applying patches to prevent authentication bypass attacks.

• Unauthenticated attackers can log in as any existing WordPress user, including administrators.
• The security nonce required to invoke the login flow is publicly exposed.

Technical summary

The WooCommerce - Social Login plugin for WordPress is vulnerable to Authentication Bypass 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. This vulnerability allows 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. The security nonce required to invoke the login flow is publicly exposed to unauthenticated users via a localized JavaScript object on the login page, which can be used in conjunction with a forged

Defensive priority

Defenders should prioritize verifying the plugin version and applying the necessary patches to prevent authentication bypass attacks.

Recommended defensive actions

• Verify the plugin version and apply patches
• Review and update the plugin configuration
• Monitor for suspicious login activity
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability. However, the exact scope of affected versions and systems requires further verification by defenders, who should check the plugin version, review system logs for suspicious activity, and verify the integrity of the plugin's configuration. The security nonce required to invoke the login flow being publicly exposed to unauthenticated users via a localized JavaScript object on the login page may impact the vulnerability's exploitability.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.