dbcve.org
Woocommerce Social LoginWordPress extension · Wpwebelite

CVE-2024-37502

HIGH · 7.5 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 2.7.0 or later.
See remediation →
84/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
Deserialization of Untrusted Data vulnerability in wpweb WooCommerce Social Login woo-social-login.This issue affects WooCommerce Social Login: from n/a through <= 2.6.3.

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 · moderate confidence

A deserialization of untrusted data vulnerability exists in the wpweb WooCommerce Social Login plugin (versions <= 2.6.3). This type of vulnerability occurs when the application deserializes data from untrusted sources without proper validation, potentially allowing attackers to manipulate serialized objects to achieve remote code execution or other malicious outcomes.

MitigationUpdate to the latest version of the WooCommerce Social Login plugin as soon as a patched release is available. If no patched version exists, consider disabling the plugin or implementing additional input validation/controls around the affected deserialization mechanism.

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.0

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
None

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

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. Confirm the WooCommerce Social Login plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'WooCommerce Social Login' by Wpwebelite, or check for the plugin directory at wp-content/plugins/woocommmerce-social-login/
    Affected if The plugin is not installed or not present in the system
  2. Check if the plugin is active
    In WordPress admin > Plugins, verify the plugin status shows as 'Active'
    Affected if The plugin is inactive or disabled - the vulnerability does not apply when the plugin is not running
  3. Identify the installed plugin version
    Access the plugin file header: open wp-content/plugins/woocommmerce-social-login/woocommmerce-social-login.php and look for the 'Version:' field in the plugin comment header, or view the plugin details in WordPress admin > Plugins
    Affected if Unable to determine version from plugin files
  4. Compare against vulnerable version range
    Compare the installed version number to the affected range: versions 2.6.3 and below are vulnerable; version 2.7.0 and above are patched. For example, if installed version is 2.6.3, 2.6.2, or any lower version, the system is affected.
    Affected if Installed version is less than 2.7.0 (e.g., 2.6.3, 2.6.2, 2.5.0, etc.)

You are affected if the WooCommerce Social Login plugin by Wpwebelite is installed, active, and running version 2.6.3 or lower; the vulnerability does not apply if the plugin is not installed, not active, or version is 2.7.0 or higher.

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.0 or later
Fixed in 2.7.0
Interim mitigation

Update to the latest version of the WooCommerce Social Login plugin as soon as a patched release is available. If no patched version exists, consider disabling the plugin or implementing additional input validation/controls around the affected deserialization mechanism.

Recommended fix High confidence

2.7.0

  1. 1. Create a full backup of your WordPress site and database before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. 3. Find 'WooCommerce Social Login' in the plugin list
  4. 4. Click 'Update now' if an update is available, or manually upload version 2.7.0 from the WordPress plugin repository
  5. 5. After updating, verify the plugin version shows 2.7.0 or higher in the plugins list
  6. 6. Test social login functionality to confirm the plugin continues to work correctly

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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