dbcve.org
CWE-288Weakness · CWE-288

CVE-2026-57807

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

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
Authentication Bypass Using an Alternate Path or Channel vulnerability in miniOrange Security Software Pvt Ltd. OAuth Single Sign On - SSO (OAuth Client) allows Password Recovery Exploitation. This issue affects OAuth Single Sign On - SSO (OAuth Client): from n/a through 38.5.8.

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 · moderate confidence

The vulnerability is an authentication bypass in miniOrange's OAuth SSO WordPress plugin that allows attackers to bypass authentication through the password recovery mechanism via an alternate path or channel. The flaw affects versions up to 38.5.8 and enables unauthorized access by exploiting the OAuth callback or password reset flow.

MitigationUpgrade to version 38.5.9 or later. Until patch is applied, disable OAuth SSO functionality and enforce alternative authentication mechanisms.

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
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 if miniOrange OAuth SSO plugin is installed
    Check WordPress plugins directory for 'miniorange-oauth-sso' or 'miniorange-wordpress-sso' folder, or view installed plugins in WP admin under Plugins > Installed Plugins
    Affected if The plugin folder or entry exists in the WordPress installation
  2. Determine installed plugin version
    Open the main plugin file (e.g., miniorange_oauth_sso.php) and look for 'Version:' in the plugin header comment, or check WordPress admin Plugins list for the version number
    Affected if The version number is 38.5.8 or lower (any version up to and including 38.5.8)
  3. Verify OAuth SSO functionality is active
    Check plugin settings at Settings > miniOrange SSO > OAuth/OIDC SSO or inspect database wp_options table for mo_oauth_* configuration keys with values indicating enabled state
    Affected if OAuth SSO configuration exists and shows enabled status, meaning authentication flows are actively processed by the vulnerable plugin
  4. Confirm password recovery or OAuth callback endpoints are accessible
    Test access to /wp-login.php?action=lostpassword or /mo_oauth_callback endpoints - verify they respond without requiring valid authentication
    Affected if These endpoints are reachable and process requests without forcing complete authentication, indicating the alternate path is exploitable

User is affected if miniOrange OAuth SSO plugin versions 38.5.8 or below is installed with OAuth functionality enabled, as the authentication bypass via password recovery or OAuth callback is then active in the environment.

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

Upgrade to version 38.5.9 or later. Until patch is applied, disable OAuth SSO functionality and enforce alternative authentication mechanisms.

Recommended fix Moderate confidence

Latest version after 38.5.8 (check WordPress plugin repository for current release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the miniOrange OAuth Single Sign On - SSO (OAuth Client) plugin
  4. Check the current installed version (should be 38.5.8 or lower)
  5. Click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository or miniOrange
  6. After updating, verify the new version number reflects the update
  7. Test the OAuth login and password recovery functionality to confirm the vulnerability is remediated

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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