# CVE-2022-3926: WP OAuth Server < 3.4.2 - Client Secret Regeneration via CSRF

> Attackers can force logged-in admins to regenerate OAuth client secrets via CSRF, potentially disrupting authentication for specific clients.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-crph-m3vh-q24g

## What is CVE-2022-3926?

CVE-2022-3926 is a medium-severity vulnerability in Unknown WP OAuth Server (OAuth Authentication), published on 5 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The WP OAuth Server (OAuth Authentication) WordPress plugin before 3.4.2 does not have CSRF check when regenerating secrets, which could allow attackers to make logged in admins regenerate the secret of an arbitrary client given they know the client ID

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Wp-Oauth Wp Oauth Server.

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

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

## Is CVE-2022-3926 being exploited?

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

## Other vulnerabilities in Unknown WP OAuth Server (OAuth Authentication)

- [CVE-2022-3892](https://insights.sbomify.com/CVE-2022-3892/): WP OAuth Server < 4.2.2 - Admin+ Stored XSS (medium 4.8)
- [CVE-2024-31253](https://insights.sbomify.com/CVE-2024-31253/): WordPress WP OAuth Server (OAuth Authentication) plugin <= 4.3.3 - Open Redirection vulnerability (medium 4.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3926 is a medium-severity vulnerability in Unknown WP OAuth Server (OAuth Authentication), published on 5 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3926 exists.

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

## Sources

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

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