# CVE-2022-2083: Simple Single Sign On <= 4.1.0 - Authentication Bypass

> Attackers can gain unauthorized access to WordPress sites by exploiting leaked OAuth client secrets in the Simple Single Sign On plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 5 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-75hr-42cm-p5wq

## What is CVE-2022-2083?

CVE-2022-2083 is a high-severity authentication bypass vulnerability in Unknown Simple Single Sign On, published on 5 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Simple Single Sign On WordPress plugin through 4.1.0 leaks its OAuth client_secret, which could be used by attackers to gain unauthorized access to the site.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Simple Sign on Project Simple Sign On.

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

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

## Is CVE-2022-2083 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2083 is a high-severity authentication bypass vulnerability in Unknown Simple Single Sign On, published on 5 Sep 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-2083 in the wild and no public exploit code.

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

## Sources

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

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