# CVE-2022-3180: WPGateway <= 3.5 - Unauthenticated Privilege Escalation

> Unauthenticated attackers can create arbitrary administrator accounts in the WPGateway WordPress plugin, leading to full site compromise.

- **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:** 11 Feb 2025
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-7xf9-6rpx-2c4r

## What is CVE-2022-3180?

CVE-2022-3180 is a critical vulnerability in Jack Hopman WPGateway, published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WPGateway Plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 3.5. This allows unauthenticated attackers to create arbitrary malicious administrator accounts.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: Wpgateway Wpgateway.

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

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

## Is CVE-2022-3180 being exploited?

There is no known exploitation of CVE-2022-3180 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3180 is a critical vulnerability in Jack Hopman WPGateway, published on 11 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-3180 in the wild and no public exploit code.

Affected product: Jack Hopman WPGateway. 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-3180/ (Markdown: https://insights.sbomify.com/CVE-2022-3180/index.md)
```

## Sources

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

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