WooCommerce Social Login <= 2.8.2 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.8.3
- Affected Plugin
- WooCommerce - Social Login
- Affected Version
<= 2.8.2- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-39472
At a glance
CVE-2025-39472 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WooCommerce - Social Login WordPress plugin, affecting versions <= 2.8.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.8.3; sites on affected versions should update now. Disclosed April 2025, reported by Ananda Dhakal.
Vulnerability Overview
The WooCommerce - Social Login plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.8.2. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action granted they can trick a site administrator into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in WooCommerce - Social Login <= 2.8.2 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WooCommerce - Social Login the fix is 2.8.3: builds <= 2.8.2 are affected, anything from 2.8.3 onward is not.
Remediation
Update to version 2.8.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WooCommerce - Social Login: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WooCommerce - Social Login 2.8.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WooCommerce - Social Login
- 9.8CVE-2026-8457: WooCommerce - Social Login Authentication Bypass
CVE-2026-8457 - 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C