dbcve.org
Woocommerce Social LoginWordPress extension · Wpwebelite

CVE-2025-39472

HIGH · 8.8 CVSS v3.1 Published 2025-04-16
Fix available
A fix is available. Upgrade to 2.8.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in wpweb WooCommerce Social Login woo-social-login allows Cross Site Request Forgery.This issue affects WooCommerce Social Login: from n/a through < 2.8.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 · high confidence

A Cross-Site Request Forgery (CSRF) vulnerability exists in the wpweb WooCommerce Social Login plugin (versions prior to 2.8.3). The plugin fails to properly validate anti-CSRF tokens (nonces) on state-changing operations, allowing attackers to trick authenticated users into performing unintended actions such as modifying social login settings or associating their accounts with attacker-controlled social profiles.

MitigationUpgrade to WooCommerce Social Login version 2.8.3 or later which includes proper CSRF token validation. Alternatively, if immediate upgrade is not possible, implement WordPress nonce verification on all form submissions and AJAX actions within the plugin.

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.8.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WooCommerce Social Login' by Wpwebelite, or check the /wp-content/plugins/ directory for the woocommerce-social-login folder
    Affected if The plugin is installed and active
  2. Check the installed version
    In WordPress admin, go to Plugins > Installed Plugins, find WooCommerce Social Login, and note the version number displayed below the plugin name
    Affected if Version is less than 2.8.3 (for example 2.8.2, 2.8.1, 2.7.0, etc.)
  3. Confirm the plugin is in use
    Navigate to WooCommerce > Settings > Social Login in the admin panel and check if any social login providers (Facebook, Google, etc.) are configured or enabled
    Affected if The plugin has active social login configurations and is processing user authentications
  4. Verify nonce validation is absent
    Examine the plugin's PHP files (particularly in includes/class-*.php or templates/) for form submissions and AJAX actions; look for missing wp_verify_nonce, check_admin_referer, or nonce_field calls on state-changing functions
    Affected if State-changing operations lack nonce verification code

You are affected if WooCommerce Social Login version 2.8.3 or higher is not installed and the plugin is actively handling social login operations on your site.

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.8.3 or later
Fixed in 2.8.3
Interim mitigation

Upgrade to WooCommerce Social Login version 2.8.3 or later which includes proper CSRF token validation. Alternatively, if immediate upgrade is not possible, implement WordPress nonce verification on all form submissions and AJAX actions within the plugin.

Recommended fix High confidence

2.8.3

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Log in to your WordPress admin dashboard
  3. 3. Navigate to Plugins > Installed Plugins
  4. 4. Find 'WooCommerce Social Login' in the plugin list
  5. 5. Click on 'Update now' if an update is available, or manually upload version 2.8.3 of the plugin
  6. 6. After updating, verify the plugin is active and functioning correctly
  7. 7. Test the social login functionality to ensure the update did not break existing features

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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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