# CVE-2022-4693: User Verification < 1.0.94 - Authentication Bypass

> Attackers can bypass authentication using known usernames to gain administrative access to the website.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2023
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-qm75-wj63-4j3j

## What is CVE-2022-4693?

CVE-2022-4693 is a critical authentication bypass vulnerability in Unknown User Verification, published on 23 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The User Verification WordPress plugin before 1.0.94 was affected by an Auth Bypass security vulnerability. To bypass authentication, we only need to know the user’s username. Depending on whose username we know, which can be easily queried because it is usually public data, we may even be given an administrative role on the website.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Pickplugins User Verification.

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

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

## Is CVE-2022-4693 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4693 is a critical authentication bypass vulnerability in Unknown User Verification, published on 23 Jan 2023. 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-4693 exists.

Affected product: Unknown User Verification. 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-4693/ (Markdown: https://insights.sbomify.com/CVE-2022-4693/index.md)
```

## Sources

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

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