# CVE-2022-3632: OAuth Client by DigitialPixies <= 1.1.0 - CSRF

> Attackers can trick logged-in users into performing unwanted actions via CSRF in the OAuth Client WordPress plugin.

- **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:** 14 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-44q8-q54p-39fv

## What is CVE-2022-3632?

CVE-2022-3632 is a medium-severity vulnerability in Unknown OAuth Client by DigitialPixies, published on 14 Nov 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 OAuth Client by DigitialPixies WordPress plugin through 1.1.0 does not have CSRF checks in some places, which could allow attackers to make logged-in users perform unwanted actions.

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

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

It affects 1 product.


Products: Digitialpixies Oauth Client.

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

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

## Is CVE-2022-3632 being exploited?

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

## Other vulnerabilities in Unknown OAuth Client by DigitialPixies

- [CVE-2022-3631](https://insights.sbomify.com/CVE-2022-3631/): OAuth Client by DigitialPixies <= 1.1.0 - Admin+ Stored Cross-Site Scripting (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3632 is a medium-severity vulnerability in Unknown OAuth Client by DigitialPixies, published on 14 Nov 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-3632 exists.

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

## Sources

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

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