dbcve.org
Woocommerce Social LoginWordPress extension · Wpwebelite

CVE-2024-6636

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-20
Fix available
A fix is available. Upgrade to 2.7.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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 unauthorized modification of data due to a missing capability check on the 'woo_slg_login_email' function in all versions up to, and including, 2.7.3. This makes it possible for unauthenticated attackers to change the default role to Administrator while registering for an account.

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 lacks a capability check on the woo_slg_login_email function, allowing unauthenticated attackers to register new user accounts with Administrator privileges by manipulating the default role assignment during registration.

MitigationUpdate the plugin to version 2.7.4 or later. If immediate update is not possible, disable the plugin and audit existing administrator accounts for unauthorized access.

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
High
Integrity
High
Availability
High

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

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
    Navigate to WordPress admin dashboard > Plugins, or inspect the plugin directory /wp-content/plugins/ for a folder containing 'woocommerce-social-login' or 'wpwebelite'. Check the plugin version listed in the plugin metadata.
    Affected if The plugin is installed and active in WordPress.
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > WooCommerce Social Login. The version number is displayed below the plugin name. Alternatively, read the main plugin PHP file header for 'Version:' tag.
    Affected if The installed version is below 2.7.4.
  3. Inspect default user role setting
    In WordPress admin, go to Settings > General > New User Default Role. Verify whether the default role is set to 'Administrator' or another elevated role.
    Affected if Default user role is set to Administrator and the vulnerable plugin version is in use.
  4. Review user accounts for unauthorized administrators
    In WordPress admin, go to Users > All Users. Sort by 'Role' and filter for 'Administrator'. Check for any unfamiliar admin accounts created recently, especially with email addresses not recognized from your organization.
    Affected if Unexpected administrator accounts exist, particularly those created without manual admin action.

A user is affected if the WooCommerce Social Login plugin version is below 2.7.4 and the default user role setting permits automatic role assignment that could result in Administrator-level access for new registrations.

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 plugin to version 2.7.4 or later. If immediate update is not possible, disable the plugin and audit existing administrator accounts for unauthorized access.

Recommended fix High confidence

2.7.4

  1. 1. Create a full backup of your WordPress site (database and files) before making any changes.
  2. 2. Navigate to WordPress Admin Dashboard > Plugins.
  3. 3. Locate the 'WooCommerce - Social Login' plugin.
  4. 4. If an update is available, click 'Update Now' to install version 2.7.4.
  5. 5. Alternatively, download version 2.7.4 from the official CodeCanyon source and upload it manually via Plugins > Add New > Upload Plugin.
  6. 6. After updating, verify the plugin version displays as 2.7.4 in the Plugins list.
  7. 7. Test the social login functionality to ensure it still works correctly.
  8. 8. Confirm that the default user role setting cannot be modified by unauthenticated users (the vulnerability should be patched).

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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