# CVE-2022-2133: OAuth Single Sign On < 6.22.6 - Authentication Bypass

> Attackers can bypass authentication and log in as any user by knowing only their email address due to missing OAuth token validation.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-c6gx-cr5g-7jhp

## What is CVE-2022-2133?

CVE-2022-2133 is a medium-severity authentication bypass vulnerability in Unknown OAuth Single Sign On – SSO (OAuth Client), published on 17 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The OAuth Single Sign On WordPress plugin before 6.22.6 doesn't validate that OAuth access token requests are legitimate, which allows attackers to log onto the site with the only knowledge of a user's email address.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-2133?

It affects 1 product.


Products: Miniorange Oauth Single Sign On.

## How do I fix CVE-2022-2133?

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

## Is CVE-2022-2133 being exploited?

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

## Other vulnerabilities in Unknown OAuth Single Sign On – SSO (OAuth Client)

- [CVE-2022-34155](https://insights.sbomify.com/CVE-2022-34155/): WordPress OAuth Single Sign On – SSO (OAuth Client) Plugin <= 6.23.3 is vulnerable to Broken Authentication (high 8.8)
- [CVE-2023-1092](https://insights.sbomify.com/CVE-2023-1092/): OAuth Single Sign On - SSO (OAuth Client) - IdP Deletion via CSRF (medium 6.5)
- [CVE-2023-1093](https://insights.sbomify.com/CVE-2023-1093/): OAuth Single Sign On - SSO (OAuth Client) < 6.24.2 - IdP Discard via CSRF (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2133 and fix it if it is affected.

What it is: CVE-2022-2133 is a medium-severity authentication bypass vulnerability in Unknown OAuth Single Sign On – SSO (OAuth Client), published on 17 Jul 2022. 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-2022-2133 in the wild and no public exploit code.

Affected product: Unknown 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-2022-2133/ (Markdown: https://insights.sbomify.com/CVE-2022-2133/index.md)
```

## Sources

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

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