dbcve.org
Woocommerce Social LoginWordPress extension · Wpwebelite

CVE-2024-6637

HIGH · 7.3 CVSS v3.1 Published 2024-07-20
Fix available
A fix is available. Upgrade to 2.7.4 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The WooCommerce - Social Login plugin for WordPress is vulnerable to unauthenticated privilege escalation in all versions up to, and including, 2.7.3. This is due to a lack of brute force controls on a weak one-time password. This makes it possible for unauthenticated attackers to brute force the one-time password for any user, except an Administrator, if they know the email of user.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WooCommerce - Social Login plugin for WordPress versions up to 2.7.3 lacks brute force protection on a weak one-time password (OTP) mechanism, allowing unauthenticated attackers to brute force OTP codes for any user account (except Administrators) provided they know the target user's email address. This enables privilege escalation to the compromised user's access level.

MitigationUpdate the WooCommerce - Social Login plugin to version 2.7.4 or later. If an update is unavailable, consider disabling the plugin or implementing additional authentication controls such as rate limiting at the web application firewall level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Woocommerce Social LoginWordPress extension
Affected:< 2.7.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify plugin installation
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'WooCommerce - Social Login' by Wpwebelite, or use WP-CLI: wp plugin list --search='woocommerce-social-login'
    Affected if The plugin is installed and active
  2. Determine installed version
    Check the plugin version number in the plugin description on the Plugins page, or run: wp plugin get woocommerce-social-login --format=json
    Affected if Version is 2.7.3 or lower (any version below 2.7.4)
  3. Verify plugin is active
    Confirm the plugin status shows as 'Active' in the Plugins list, or check: wp plugin status woocommerce-social-login
    Affected if Plugin is active and running
  4. Check social login configuration
    Navigate to WooCommerce > Settings > Social Login in the WordPress admin, or inspect the wp_options table for option_name containing 'wc_social_login' settings
    Affected if Any social login provider (Facebook, Google, Twitter, etc.) is configured and enabled

If the plugin is active, installed version is below 2.7.4, and social login providers are configured, the environment is vulnerable to OTP brute force attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.7.4 or later
Fixed in 2.7.4
Interim mitigation

Update the WooCommerce - Social Login plugin to version 2.7.4 or later. If an update is unavailable, consider disabling the plugin or implementing additional authentication controls such as rate limiting at the web application firewall level.

Recommended fix High confidence

2.7.4

  1. Back up your WordPress site database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find the WooCommerce Social Login plugin
  4. Click 'Update now' if an update is available, or manually upload version 2.7.4 of the plugin
  5. After updating, verify the plugin version shows 2.7.4
  6. Test the social login functionality to ensure the fix does not break legitimate functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Woocommerce Social Login Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6637 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6637 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data