dbcve.org
Social LoginWordPress extension · Miniorange

CVE-2024-11087

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-08
Fix available
A fix is available. Upgrade to after 200.3.9 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 miniOrange Social Login and Register (Discord, Google, Twitter, LinkedIn) Pro Addon plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 200.3.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 username 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 miniOrange Social Login plugin for WordPress fails to properly validate that the social login token corresponds to the intended user account. Attackers can craft authentication requests using valid usernames, bypassing the social login verification to authenticate as any existing user (including administrators) if the target user hasn't yet linked that social service to their WordPress account.

MitigationUpdate the miniOrange Social Login and Register Pro Addon to the latest version beyond 200.3.9. If immediate update is not possible, temporarily disable the social login functionality and monitor for unauthorized administrative access.

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
Social LoginWordPress extension
Affected:<= 200.3.9

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 installed plugin version
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, locate 'miniOrange Social Login' and note the version number displayed. Alternatively, inspect the plugin's main PHP file (typically miniorange_login_openid.php in wp-content/plugins/) and look for the 'Version' header in the file comments.
    Affected if The displayed version number is 200.3.9 or lower.
  2. Verify social login providers are configured
    Access the plugin settings page in WordPress admin (usually under Users > Social Login or a dedicated miniOrange settings menu). Look for configured social providers such as Google, Facebook, Twitter, or other OAuth/OpenID providers.
    Affected if At least one social login provider is enabled and configured on the site.
  3. Confirm social login is active on login pages
    Inspect your WordPress login page (wp-login.php) or any frontend login forms. Look for social login buttons/widgets provided by the miniOrange plugin. Check the plugin settings to confirm the social login form is set to display on the login page.
    Affected if Social login buttons or forms are present and active on the site's login page.
  4. Assess user linking status
    Review user accounts in WordPress admin (Users > All Users). For each user account, check if a social account has been linked by inspecting user profile fields or the plugin's user meta data. Alternatively, query the WordPress usermeta table for records containing 'mo_openid' or social provider identifiers.
    Affected if Users exist who have NOT linked any social service to their WordPress account - these accounts are vulnerable to takeover.

You are affected if the miniOrange Social Login plugin version is 200.3.9 or lower, social login providers are enabled, and any users (especially administrators) have not yet linked their social accounts to their WordPress profiles.

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 a release after 200.3.9
Interim mitigation

Update the miniOrange Social Login and Register Pro Addon to the latest version beyond 200.3.9. If immediate update is not possible, temporarily disable the social login functionality and monitor for unauthorized administrative access.

Recommended fix Moderate confidence

Latest version available from WordPress plugin repository (version > 200.3.9)

  1. Check the WordPress admin dashboard for plugin updates under Dashboard > Updates
  2. Update the miniOrange Social Login and Register plugin to the latest available version
  3. After updating, verify that social login functionality continues to work correctly
  4. Ensure any users who may have been affected are reviewed and their accounts are secure
  5. Consider enabling two-factor authentication for administrative accounts as an additional security measure

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

Fix this in Social Login Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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