Stop User Enumeration 1.3.8 allows user enumeration via the REST API

published 2017-11-17 8y ago modified 2026-06-17 4mo ago also EUVD-2017-1495

cvss: 5.3; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.4%; EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits: 0; none known

Is CVE-2017-1000226 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.39% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

security.dxw.com https://security.dxw.com/advisories/stop-user-enumeration-rest-api/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.3	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

Technology feeds

WordPress rss critical rss

References

security.dxw.com /advisories/stop-user-enumeration-rest-api/
exploit, third-party-advisory

Sources

CVE List CVE-2017-1000226
NVD CVE-2017-1000226

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.