# CVE-2026-57807: WordPress OAuth Single Sign On - SSO (OAuth Client) plugin <= 38.5.8 - Broken Authentication vulnerability

> Attackers can bypass authentication via password recovery exploitation in the WordPress OAuth SSO plugin, leading to account takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-x77p-gjm6-3v9r

## What is CVE-2026-57807?

CVE-2026-57807 is a critical authentication bypass vulnerability in miniOrange Security Software Pvt Ltd. OAuth Single Sign On - SSO (OAuth Client), published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2026-57807?


## How do I fix CVE-2026-57807?

No fix has been published for CVE-2026-57807 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-57807 being exploited?

There is no known exploitation of CVE-2026-57807 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57807 and fix it if it is affected.

What it is: CVE-2026-57807 is a critical authentication bypass vulnerability in miniOrange Security Software Pvt Ltd. OAuth Single Sign On - SSO (OAuth Client), published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57807 in the wild and no public exploit code.

Affected product: miniOrange Security Software Pvt Ltd. OAuth Single Sign On - SSO (OAuth Client). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57807/ (Markdown: https://insights.sbomify.com/CVE-2026-57807/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57807
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57807
- OSV: https://osv.dev/vulnerability/CVE-2026-57807

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57807/
Summaries are generated and may contain mistakes; the official description above is the record.