dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2024-10111

HIGH · 8.1 CVSS v3.1 Published 2024-12-12
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 OAuth Single Sign On – SSO (OAuth Client) plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 6.26.3. 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 OAuth SSO plugin for WordPress fails to properly validate the user identity returned by the OAuth provider's token, allowing an attacker to authenticate as any existing site user (including administrators) by supplying a valid username without that user having a linked OAuth account.

MitigationUpdate the plugin to version 6.26.4 or later. If immediate update is not possible, consider disabling the plugin or implementing additional authentication controls.

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 the OAuth SSO plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for any OAuth, SSO, or OAuth SSO related plugin. Alternatively, check the wp-content/plugins/ directory for folders containing 'oauth' or 'sso' in the name.
    Affected if The OAuth SSO plugin is installed and active
  2. Check the plugin version against the threshold
    In WordPress admin, click on the plugin to view its details and find the version number. Compare this to version 6.26.4 - versions below 6.26.4 are vulnerable.
    Affected if The installed version is below 6.26.4
  3. Verify OAuth SSO functionality is enabled
    Navigate to the plugin settings (usually under Settings > OAuth SSO or similar) and check if OAuth single sign-on is currently enabled or configured.
    Affected if OAuth SSO is enabled and configured for user authentication
  4. Check user account linking configuration
    Review the plugin settings to determine how users are linked to OAuth accounts. Look for options controlling whether usernames must be pre-linked or can be created on-the-fly.
    Affected if The plugin allows authentication with usernames that have no linked OAuth account

A user is affected if the OAuth SSO plugin is installed with a version below 6.26.4 and OAuth authentication is enabled, regardless of user account linking configuration.

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 6.26.4 or later. If immediate update is not possible, consider disabling the plugin or implementing additional authentication controls.

Recommended fix High confidence

6.26.4 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'OAuth Single Sign On – SSO (OAuth Client)' plugin
  4. Check if the current version is 6.26.3 or earlier
  5. If vulnerable, click 'Update Now' to update to version 6.26.4 or later
  6. Alternatively, navigate to Dashboard > Updates and update all plugins
  7. After updating, verify the new version number in the plugins list

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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