# CVE-2022-3892: WP OAuth Server < 4.2.2 - Admin+ Stored XSS

> Admins can inject malicious scripts via Client IDs in WP OAuth Server, leading to stored XSS attacks even in restricted multisite environments.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-mqjq-qch6-x888

## What is CVE-2022-3892?

CVE-2022-3892 is a medium-severity cross-site scripting vulnerability in Unknown WP OAuth Server (OAuth Authentication), published on 5 Dec 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The WP OAuth Server (OAuth Authentication) WordPress plugin before 4.2.2 does not sanitize and escape Client IDs, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)

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

It affects 1 product.


Products: Wp-Oauth Wp Oauth Server.

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

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

## Is CVE-2022-3892 being exploited?

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

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

- [CVE-2022-3926](https://insights.sbomify.com/CVE-2022-3926/): WP OAuth Server < 3.4.2 - Client Secret Regeneration via CSRF (medium 6.5)
- [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-3892 and fix it if it is affected.

What it is: CVE-2022-3892 is a medium-severity cross-site scripting vulnerability in Unknown WP OAuth Server (OAuth Authentication), published on 5 Dec 2022. An attacker needs administrator access to exploit it, 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-3892 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-3892/ (Markdown: https://insights.sbomify.com/CVE-2022-3892/index.md)
```

## Sources

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

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