dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2024-11293

HIGH · 8.1 CVSS v3.1 Published 2024-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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 Registration Forms – User Registration Forms, Invitation-Based Registrations, Front-end User Profile, Login Form & Content Restriction Social Sites Login plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 1.7.9. 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 confidence

The plugin fails to properly validate users returned by social login tokens, allowing unauthenticated attackers to authenticate as any existing user (including administrators) by providing a valid email address from a social login provider without the user having previously linked that social account.

MitigationUpdate the plugin to version 1.8.0 or later which implements proper token validation and user verification. Consider disabling social login functionality until the patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify social login plugin installation
    Check the WordPress plugins directory for any installed social login authentication plugin (such as miniOrange Social Login, Nextend Social Login, or similar). Use 'wp plugin list' or inspect the /wp-content/plugins/ directory.
    Affected if A social login plugin is installed and active in WordPress
  2. Check plugin version against vulnerable range
    Retrieve the installed plugin version from the plugin header or WordPress admin panel. Compare it to the affected version range (versions prior to the patch that implements proper token validation).
    Affected if The installed plugin version is older than the patched version that fixes the token validation issue
  3. Verify social login is enabled
    Check the plugin settings to confirm if social login functionality is currently enabled for user authentication. Look for 'Enable Social Login' or similar configuration options in the plugin settings page.
    Affected if Social login is enabled and users can authenticate via social providers
  4. Check for existing social account links
    Inspect the WordPress usermeta database table for entries related to social login (commonly keys like 'facebook_id', 'google_id', 'twitter_id', or plugin-specific meta keys). Query: SELECT * FROM wp_usermeta WHERE meta_key LIKE '%social%' OR meta_key LIKE '%facebook%' OR meta_key LIKE '%google%'.
    Affected if Any user accounts have linked social authentication providers
  5. Review authentication flow configuration
    Examine the plugin configuration to determine if email verification from social providers is being validated against existing WordPress users without requiring prior social account linking.
    Affected if The plugin allows authentication via social provider email without the user having previously linked that social account to their WordPress account

A user is affected if they have an active social login plugin installed with social login enabled, and the plugin version is vulnerable to improper token validation that allows authentication as any existing user by providing a valid email from a social provider.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.8.0 or later which implements proper token validation and user verification. Consider disabling social login functionality until the patch is applied.

Recommended fix High confidence

Upgrade to version 1.8.0 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the 'Registration Forms – User Registration Forms, Invitation-Based Registrations, Front-end User Profile, Login Form & Content Restriction Social Sites Login' plugin
  4. Click 'Update now' if an update is available, or manually update to version 1.8.0 or later
  5. Verify the plugin version shows 1.8.0 or higher after updating
  6. Review user accounts for any suspicious or unauthorized administrators that may have been created during an attack
  7. Consider resetting passwords for high-privilege users as a precaution

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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