dbcve.org
Woocommerce Social LoginWordPress extension · Wpwebelite

CVE-2024-7503

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-12
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 authentication bypass in versions up to, and including, 2.7.5. This is due to the use of loose comparison of the activation code in the 'woo_slg_confirm_email_user' function. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the userID. This requires the email module to be enabled.

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.5 contains an authentication bypass vulnerability in the woo_slg_confirm_email_user function. The vulnerability stems from using loose comparison (==) instead of strict comparison (===) when validating the activation code, allowing unauthenticated attackers to authenticate as any existing user by providing a valid userID.

MitigationUpdate the plugin to version 2.7.6 or later. As a temporary workaround, disable the email module until the update can be applied.

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. Identify plugin and version
    Go to WordPress admin > Plugins > Installed Plugins and locate 'WooCommerce Social Login' by Wpwebelite. Note the installed version number.
    Affected if The installed version is lower than 2.7.4 (e.g., 2.7.3, 2.7.2, etc.)
  2. Verify email module is active
    Navigate to WooCommerce > Settings > Social Login in the WordPress admin. Check if the Email option is enabled under the available login methods.
    Affected if The email module is enabled and the plugin version is below 2.7.4
  3. Confirm plugin files exist
    Access the site via FTP or file manager and navigate to /wp-content/plugins/woocommerce-social-login/. Verify the main plugin file woocommerce-social-login.php exists.
    Affected if The plugin directory exists and contains the vulnerable code file
  4. Check for vulnerable function
    Examine the file includes/social/wooslg-social.php or similar file containing the woo_slg_confirm_email_user function. Search for the loose comparison pattern used in activation code validation.
    Affected if The function uses == (loose comparison) instead of === (strict comparison) for validating activation codes

A user is affected if they have WooCommerce Social Login installed with version 2.7.3 or lower and have the email login module enabled.

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.6 or later. As a temporary workaround, disable the email module until the update can be applied.

Recommended fix High confidence

Latest version of WooCommerce Social Login (version 2.7.4 or higher)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate WooCommerce Social Login plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository or CodeCanyon and upload manually
  6. 6. Verify the updated version number reflects the patched release
  7. 7. Confirm the email login module is still functioning correctly after 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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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