dbcve.org
Woocommerce Social LoginWordPress extension · Wpwebelite

CVE-2024-5871

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-15
Fix available
A fix is available. Upgrade to 2.6.3 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 PHP Object Injection in all versions up to, and including, 2.6.2 via deserialization of untrusted input from the 'woo_slg_verify' vulnerable parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

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 is vulnerable to PHP Object Injection via the 'woo_slg_verify' parameter. The vulnerability stems from deserialization of untrusted input without proper validation, allowing unauthenticated attackers to inject arbitrary PHP objects. While no POP chain exists in the plugin itself, additional plugins or themes on the target system could provide one, enabling remote code execution, file deletion, or data retrieval.

MitigationUpdate the plugin to the latest patched version once available, or remove/replace the plugin if no patch is forthcoming. Until patched, consider disabling social login functionality or restricting access via WAF rules targeting the vulnerable parameter.

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

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 if WooCommerce Social Login plugin is installed
    Check the WordPress plugins directory or wp-content/plugins folder for the 'woocommerce-social-login' or 'woocomerce-social-login' directory. In WordPress admin, go to Plugins > Installed Plugins and look for WooCommerce Social Login by Wpwebelite.
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > WooCommerce Social Login. The version number is displayed below the plugin name. Alternatively, check the main plugin file (e.g., woocommerce-social-login.php) for the 'Version' header in the plugin comment block.
    Affected if The version is below 2.6.3 (any version starting with 2.6.2, 2.6.1, 2.6.0, 2.5.x, 2.4.x, etc.)
  3. Check if the vulnerable parameter is accessible
    Inspect HTTP requests to the WordPress site. The vulnerability is in the 'woo_slg_verify' parameter. This parameter is typically submitted via POST or GET to an endpoint that handles social login verification (often the WordPress admin-ajax.php or a front-end endpoint).
    Affected if The site processes the 'woo_slg_verify' parameter without sanitization (the site is affected regardless of version if the parameter is processed, but version determines the presence of the vulnerability)

A user is affected if the WooCommerce Social Login plugin by Wpwebelite is installed with any version prior to 2.6.3 and the site processes the 'woo_slg_verify' parameter.

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.6.3 or later
Fixed in 2.6.3
Interim mitigation

Update the plugin to the latest patched version once available, or remove/replace the plugin if no patch is forthcoming. Until patched, consider disabling social login functionality or restricting access via WAF rules targeting the vulnerable parameter.

Recommended fix High confidence

2.6.3

  1. 1. Back up your WordPress site database and files before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins > Installed Plugins.
  3. 3. Locate the 'WooCommerce - Social Login' plugin.
  4. 4. If an update is available, click 'Update Now' to install version 2.6.3 or later.
  5. 5. Alternatively, download version 2.6.3 from the official CodeCanyon source (codecanyon.net).
  6. 6. Deactivate the existing plugin, then delete it, and upload/install the new version 2.6.3.
  7. 7. After update, verify the plugin is active and functioning correctly.
  8. 8. Confirm the plugin version displayed in the plugins list shows 2.6.3 or higher.
Caveat Review any customizations or integrations with social login functionality after upgrade to ensure compatibility

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

Fix this in Woocommerce Social Login Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
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,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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