# CVE-2025-4302: Stop User Enumeration < 1.7.3 - Protection Bypass

- Exploited (CISA KEV): no
- Published: 2025-07-17
- CVSS: 5.3 MEDIUM (v3.1)
- EPSS: 1.0% (62th percentile)

The Stop User Enumeration WordPress plugin before version 1.7.3 blocks REST API /wp-json/wp/v2/users/ requests for non-authorized users. However, this can be bypassed by URL-encoding the API path.

## Edge WAF coverage (claimed by vendors, not measured)

| Vendor | Status | First rule | Days after publication |
|---|---|---|---|
| Cloudflare | No public claim | — | — |
| AWS | No public claim | — | — |
| Microsoft Azure | No public claim | — | — |
| Google Cloud | No public claim | — | — |
| Fastly | Before feed history | — | — |
| F5 | Rule published | 2025-12-03 | 139 |
| Akamai | No public source | — | — |
| OWASP CRS | No public claim | — | — |

### F5

- 2025-12-03 · new · rule 200009345
  > Added: signature 200009345 "Stop User Enumeration Plugin Information Leakage" (Information Leakage, risk Medium), systems: WordPress. References: CVE-2025-4302.
  Source: https://docs.cloud.f5.com/docs-v2/platform/changelogs/security-details-changelog
- 2025-12-03 · new · rule 200009346
  > Added: signature 200009346 "Stop User Enumeration Plugin Information Leakage (2)" (Information Leakage, risk Medium), systems: WordPress. References: CVE-2025-4302.
  Source: https://docs.cloud.f5.com/docs-v2/platform/changelogs/security-details-changelog

## Our test (measured)

- OWASP Core Rule Set 4.25.0, paranoia level 1, anomaly threshold 5, default CRS settings: passed (0 of 2 requests blocked), template CVE-2025-4302, 2026-11-02
- OWASP Core Rule Set 4.25.0, paranoia level 2, anomaly threshold 5, default CRS settings: passed (0 of 2 requests blocked), template CVE-2025-4302, 2026-11-02

"No public claim" means no vendor statement names this CVE; "Before feed history" means the CVE is older than the vendor feed. In both cases generic rules may still block it.

HTML: https://cve.vigilbase.com/cve/CVE-2025-4302 · JSON: https://cve.vigilbase.com/api/v1/cves/CVE-2025-4302