dbcve.org
Woocommerce Social LoginWordPress extension · Wpwebelite

CVE-2024-6635

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 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 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 versions up to 2.7.3 contain an authentication bypass vulnerability in the woo_slg_login_email function. This function lacks sufficient validation controls, allowing unauthenticated attackers to log in as any existing user on the site by simply knowing the user's email address, provided the target is not an administrator account.

MitigationUpdate the WooCommerce Social Login plugin to the latest patched version as soon as available. Until a patch is released, consider disabling the plugin or implementing additional authentication controls such as requiring additional verification for email-based login attempts.

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. Verify WooCommerce Social Login plugin is installed
    Go to WordPress admin > Plugins and look for 'WooCommerce Social Login' by Wpwebelite, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' (adjust prefix if different)
    Affected if Plugin is not installed or not found in the plugin list
  2. Check installed plugin version
    In WordPress admin > Plugins > WooCommerce Social Login, view the plugin details to see the version number, or inspect the main plugin file header for the Version field
    Affected if Version is 2.7.3 or lower (any version less than 2.7.4)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify the WooCommerce Social Login plugin is currently activated
    Affected if Plugin is active and vulnerable function is reachable
  4. Identify non-administrator user accounts
    In WordPress admin > Users, review the list of existing users. Note that administrators are explicitly not affected by this vulnerability
    Affected if There are user accounts with roles other than Administrator (Subscriber, Customer, Editor, Author, Contributor)

If the WooCommerce Social Login plugin version is below 2.7.4 and the plugin is active, and there are non-administrator user accounts on the site, the environment is vulnerable to unauthenticated login via known email addresses.

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 the latest patched version as soon as available. Until a patch is released, consider disabling the plugin or implementing additional authentication controls such as requiring additional verification for email-based login attempts.

Recommended fix High confidence

2.7.4

  1. Create a complete backup of your WordPress site before making any changes
  2. Update the WooCommerce Social Login plugin to version 2.7.4 or later through the WordPress admin dashboard (Plugins > Add New > Upload or directly from the WordPress plugin repository)
  3. Alternatively, update via WP-CLI: wp plugin update woocommerce-social-login
  4. Verify the plugin version shows 2.7.4 or higher in the installed plugins list
  5. Test the social login functionality to ensure legitimate users can still authenticate properly
  6. Consider reviewing user accounts to ensure no unauthorized access occurred prior to the update

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

Fix this in Woocommerce Social Login Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6635 — 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-6635 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