CVE-2024-6635

WooCommerce - Social Login <= 2.7.3 - Unauthenticated Authentication Bypass

2024-07-19 00:00
Vu Nguyen (maxntv)

Strategic Overview

Status
Patched in 2.7.4
Affected Plugin
WooCommerce - Social Login
Affected Version
<= 2.7.3
CVSS
7.3High
Weakness type
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
CVE
CVE-2024-6635
View all WooCommerce - Social Login vulnerabilities

At a glance

CVE-2024-6635 is a high-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the WooCommerce - Social Login WordPress plugin, affecting versions <= 2.7.3. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.7.4; sites on affected versions should update now. Disclosed July 2024, reported by Vu Nguyen (maxntv).

Vulnerability Overview

The WooCommerce - Social Login plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.7.3. This is due to insufficient controls in the 'woo_slg_login_email' function. This makes it possible for unauthenticated attackers to log in as any existing user on the site, excluding an administrator, if they know the email of user.

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.

CWE-288: Authentication Bypass Using an Alternate Path or Channel

WooCommerce - Social Login <= 2.7.3 carries this weakness at woo_slg_login_email, and reaching it takes no account at all. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.

The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For WooCommerce - Social Login the fix is 2.7.4: builds <= 2.7.3 are affected, anything from 2.7.4 onward is not.

Remediation

Update to version 2.7.4, 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.7.4 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-6635https://www.wordfence.com/threat-intel/vulnerabilities/id/37836722-eb25-4393-8cdf-91057642ba3fhttps://nvd.nist.gov/vuln/detail/CVE-2024-6635

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C