# CVE-2022-3119: OAuth client Single Sign On for WordPress < 3.0.4 - Unauthenticated Settings Update to Authentication Bypass

> Unauthenticated attackers can modify OAuth settings to bypass authentication and gain admin access if they know the target email address.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 26 Sep 2022
- **Updated:** 21 May 2025
- **Also known as:** GHSA-wh77-xq95-gvgr

## What is CVE-2022-3119?

CVE-2022-3119 is a high-severity missing authorization vulnerability in Unknown OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ), published on 26 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The OAuth client Single Sign On WordPress plugin before 3.0.4 does not have authorisation and CSRF when updating its settings, which could allow unauthenticated attackers to update them and change the OAuth endpoints to ones they controls, allowing them to then be authenticated as admin if they know the correct email address

Weakness: CWE-352 (Cross-Site Request Forgery), CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Oauth Client Single Sign on Project Oauth Client Single Sign On.

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

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

## Is CVE-2022-3119 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3119 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3119 is a high-severity missing authorization vulnerability in Unknown OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ), published on 26 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3119 exists.

Affected product: Unknown OAuth client Single Sign On for WordPress ( OAuth 2.0 SSO ). 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-3119/ (Markdown: https://insights.sbomify.com/CVE-2022-3119/index.md)
```

## Sources

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

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