Vulnerability report

Exploitation attempts observed in the wild High confidence Not in CISA KEV

CVE-2022-3180

WPGateway <= 3.5 - Unauthenticated Privilege Escalation

Jack Hopman / WPGateway · * to <= 3.5

Severity
CVSS 9.8 · Critical
Confidence
High
Exploit status
Exploitation attempts observed in the wild
EPSS
9.2%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2022-3180 is an unauthenticated WPGateway <= 3.5 - Unauthenticated Privilege Escalation. The WPGateway Plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 3.5. This allows...

Have exploitation attempts been observed?

Yes. Exploitation attempts have been reported for this vulnerability. Previdian lists it as a known exploited vulnerability. Also reported by third-party sources. Confidence is high.

Who is affected?

Jack Hopman / WPGateway * to <= 3.5.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

The WPGateway Plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 3.5

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.

Jack Hopman Affected
WPGateway
Through 3.5
Published
11 Feb 2025
Exploitation Attempts Reported
13 Sep 2022
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

wordpress

CVE References

Exploitation evidence

Evidence of exploitation attempts

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploitation attempts observed in the wild

Wordfence

Recorded 13 Sep 2022

A trusted third party reported exploitation attempts.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
Wordfence First 2022-09-13 08:50 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

9.8 Critical

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

9.2%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Timeline

From disclosure to observed exploitation attempts

  1. 21:38 UTC

    CVE published

    Vulnerability disclosed publicly

  2. 08:50 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party report of exploitation attempts

  3. 16:10 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2022-3180

Sample API response
{
  "cve_id": "CVE-2022-3180",
  "confidence": "High",
  "cvss_score": 9.8,
  "cvss_estimated": false,
  "epss_score": 0.0921,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}