wp-includes/rest-api/endpoints/class-wp-rest-users-controller.php in the REST API implementation in WordPress 4.7 before 4.7.1 does not properly restrict listings of post authors, which allows remote attackers to obtain sensitive information via a wp-json/wp/v2/users request.
CVE-2017-5487
Score elevated to 9.0 because EPSS predicts 87% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 5.3 retained for reference. Confidence: see factors.
- High exploitation likelihood — EPSS 87%
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 9.0(high)
- EG Risk
- 80(Track)EG Risk 80/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation87% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 99.7%
- KEV
- Not listed
Published
January 15, 2017
Last Modified
May 13, 2026
References (18)
- cve@mitrehttp://www.openwall.com/lists/oss-security/2017/01/14/6
- cve@mitrehttp://www.securityfocus.com/bid/95391
- cve@mitrehttp://www.securitytracker.com/id/1037591
- cve@mitrehttps://codex.wordpress.org/Version_4.7.1
- cve@mitrehttps://github.com/WordPress/WordPress/commit/daf358983cc1ce0c77bf6d2de2ebbb43df2add60
- cve@mitrehttps://wordpress.org/news/2017/01/wordpress-4-7-1-security-and-maintenance-release/
- cve@mitrehttps://wpvulndb.com/vulnerabilities/8715
- cve@mitrehttps://www.exploit-db.com/exploits/41497/
- cve@mitrehttps://www.wordfence.com/blog/2016/12/wordfence-blocks-username-harvesting-via-new-rest-api-wp-4-7/
- af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2017/01/14/6
- af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/95391
- af854a3a-2127-422b-91ae-364da2661108http://www.securitytracker.com/id/1037591
- af854a3a-2127-422b-91ae-364da2661108https://codex.wordpress.org/Version_4.7.1
- af854a3a-2127-422b-91ae-364da2661108https://github.com/WordPress/WordPress/commit/daf358983cc1ce0c77bf6d2de2ebbb43df2add60
- af854a3a-2127-422b-91ae-364da2661108https://wordpress.org/news/2017/01/wordpress-4-7-1-security-and-maintenance-release/
Data Freshness Timeline
(refreshed 6× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 01:29 UTCEG score recompute
- 2026-07-22 22:09 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-12 05:43 UTCEPSS rescore
- 2026-07-12 04:52 UTCOSV refresh
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-02 16:54 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-23 11:00 UTCOSV refresh
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-17 17:50 UTCEPSS rescore
- 2026-06-15 17:45 UTCEPSS rescore
- 2026-06-13 22:57 UTCEPSS rescore
- 2026-06-12 23:09 UTCEPSS rescore
- 2026-06-10 22:15 UTCEPSS rescore
- 2026-06-06 12:40 UTCOSV refresh
- 2026-06-05 22:44 UTCEPSS rescore
Show 20 moreShow fewer
- 2026-05-31 00:14 UTCEPSS rescore
- 2026-05-31 00:14 UTCEPSS rescore
- 2026-05-29 13:41 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-28 13:42 UTCEPSS rescore
- 2026-05-27 13:38 UTCEPSS rescore
- 2026-05-27 13:38 UTCEPSS rescore
- 2026-05-26 13:42 UTCEPSS rescore
- 2026-05-26 13:42 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-22 21:15 UTCEPSS rescore
- 2026-05-22 17:08 UTCEG score recompute
- 2026-05-22 17:08 UTCGHSA enrichment
- 2026-05-20 22:37 UTCEPSS rescore
- 2026-05-20 22:37 UTCEPSS rescore
- 2026-05-20 22:37 UTCEPSS rescore
- 2026-05-18 21:30 UTCEPSS rescore
Publicly available exploits
(4 references)Working exploit code is in the public domain (3 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCK3ysTr0K3R/CVE-2017-5487-EXPLOITFirst seen May 6, 2023
A PoC exploit for CVE-2017-5487 - WordPress User Enumeration.
Open source ↗ - GitHub PoCpatilkr/wp-CVE-2017-5487-exploitFirst seen Apr 26, 2020
WordPress CVE-2017-5487 Exploit in Python
Open source ↗ - GitHub PoCGeunSam2/CVE-2017-5487First seen Jun 10, 2019
POC of CVE-2017-5487 + tool
Open source ↗ - Exploit-DBEDB-41497First seen Mar 3, 2017
WordPress Core < 4.7.1 - Username Enumeration
Open source ↗
Frequently asked(5)
What is CVE-2017-5487?
When was CVE-2017-5487 disclosed?
Is CVE-2017-5487 actively exploited?
What is the CVSS score of CVE-2017-5487?
How do I remediate CVE-2017-5487?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2017-5487
Is Your Infrastructure Affected by CVE-2017-5487?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.