CVE-2022-3180: The WPGateway Plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 3.5

Q: How do I fix CVE-2022-3180?

wpgateway: upgrade to newer than 3.5. Exact commands for each OS are on this page.

Q: Is CVE-2022-3180 being exploited?

CVE-2022-3180 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-3180 affect?

CVE-2022-3180 affects wpgateway. Severity is critical (CVSS 9.8). 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.

Q: How urgent is CVE-2022-3180?

Priority 63/100. Critical severity; EPSS top 5%: very likely to be exploited; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2022-3180 is a critical-severity flaw (CVSS 9.8) affecting wpgateway. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
EPSS top 5%: very likely to be exploited
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	9.2% (top 5%)
CISA exploited list	No
Weakness	CWE-290
Published	2025-02-11
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: wpgateway

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-02-11 22:15 UTCPublished CVE record published
2026-06-17 04:59 UTCUpdated Record last modified

wpgateway wpgateway UPGRADE

Affected: <= 3.5

Fixed in: newer than 3.5

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wpgateway || rpm -q wpgateway || wpgateway --version

2. UPGRADE to newer than 3.5 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wpgateway

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wpgateway

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-3180?

wpgateway: upgrade to newer than 3.5. Exact commands for each OS are on this page.

Is CVE-2022-3180 being exploited?

CVE-2022-3180 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-3180 affect?

CVE-2022-3180 affects wpgateway. Severity is critical (CVSS 9.8). 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.

How urgent is CVE-2022-3180?

Priority 63/100. Critical severity; EPSS top 5%: very likely to be exploited; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs