Woocommerce Social LoginWordPress extension · Wpwebelite
CVE-2024-10114
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 · uneditedThe WooCommerce - Social Login plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 2.7.7. This is due to insufficient verification on the user being returned by the social login token. 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 email and the user does not have an already-existing account for the service returning the token.
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 confidenceThe WooCommerce Social Login plugin fails to properly validate the OAuth/social token against the claimed user identity during the authentication process. An unauthenticated attacker can exploit this by submitting a request with a target user's email address, causing the plugin to either create a new account or associate the session with an existing administrator account without proper token verification.
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
< 2.7.8CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WooCommerce Social Login plugin is installedNavigate to WordPress admin > Plugins and look for 'WooCommerce Social Login' by Wpwebelite in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn WordPress admin > Plugins, click on the WooCommerce Social Login plugin to view its version number. Compare this version against the affected range: versions prior to 2.7.8 are vulnerableAffected if The installed version is 2.7.7 or lower (any version below 2.7.8)
-
Confirm the social login feature is activeNavigate to WooCommerce > Settings > Social Login (or the plugin's settings page) and verify that any social login provider (Facebook, Google, Twitter, etc.) is enabledAffected if At least one social login provider is enabled and configured
-
Review user accounts created via social loginIn WordPress admin > Users, examine user accounts. Check the 'Registered' column and user metadata (or use a database query) to identify users where the registration method indicates social login. Focus on accounts with Administrator roleAffected if There exist user accounts registered through social login, particularly those with Administrator role that were not intentionally created by site administrators
If the WooCommerce Social Login plugin version is below 2.7.8 AND social login is enabled, the site is vulnerable to this authentication bypass. Existing admin accounts created via social login should be investigated as potential compromise indicators.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.7.8
Update the WooCommerce Social Login plugin to version 2.7.8 or later. Review existing user accounts created via social login, especially those with administrative privileges, and consider resetting passwords for high-privilege users as a precaution.
WooCommerce Social Login version 2.7.8
- Backup your WordPress site before making any changes
- Update the WooCommerce Social Login plugin to version 2.7.8 or later through the WordPress admin dashboard (Plugins > Updates) or via wp-cli: wp plugin update woocommerce-social-login
- Verify the update was successful by checking the plugin version in Plugins > Installed Plugins
- Test that social login functionality works correctly after the update
- Ensure the site functions normally for all users
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
- Implementation1.0 h
- Testing2.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10114 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10114 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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