CVE-2017-5487

CRITICALNVD 5.39.0▲
EchelonGraph scoreHIGH confidence

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.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 1,196 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 87%
CISA-KEV: Not listedEPSS PROB: 87%CVSS: 5.3Exploit: Elevated riskExposed: 1,196

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

Live · internet exposure

1,196 internet-exposed hosts are running an affected version of CVE-2017-5487 right now.

across 48 countries (United States, Germany, United Kingdom, Australia, Singapore)top: wordpress
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

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 computed
Severity90% × 45%
Exploitation87% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
87%
EPSS %ILE
100%
KEV
Not listed

Published

January 15, 2017

Last Modified

June 17, 2026

References (18)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
wordpress—4.7.1+dfsg-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
wordpress—4.7.1+dfsg-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
wordpress—4.7.1+dfsg-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
wordpress—4.7.1+dfsg-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 9× 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.

  1. 2026-09-24 13:59 UTCEPSS rescore
  2. 2026-09-18 19:22 UTCEPSS rescore
  3. 2026-09-18 17:06 UTCOSV refresh
  4. 2026-09-12 14:55 UTCEPSS rescore
  5. 2026-09-06 13:43 UTCEPSS rescore
  6. 2026-09-05 15:23 UTCEPSS rescore
  7. 2026-09-04 13:56 UTCEPSS rescore
  8. 2026-08-30 20:38 UTCOSV refresh
  9. 2026-08-30 19:13 UTCEPSS rescore
  10. 2026-08-26 14:41 UTCEPSS rescore
  11. 2026-08-25 13:44 UTCEPSS rescore
  12. 2026-08-20 22:51 UTCEPSS rescore
  13. 2026-08-19 16:59 UTCEPSS rescore
  14. 2026-08-18 13:43 UTCEPSS rescore
  15. 2026-08-15 01:26 UTCEPSS rescore
  16. 2026-08-14 07:16 UTCOSV refresh
  17. 2026-08-12 13:46 UTCEPSS rescore
  18. 2026-08-09 13:42 UTCEPSS rescore
  19. 2026-08-06 13:42 UTCEPSS rescore
  20. 2026-07-29 14:37 UTCOSV refresh
  21. 2026-07-28 15:32 UTCEPSS rescore
  22. 2026-07-23 14:15 UTCEPSS rescore
  23. 2026-07-23 01:29 UTCEG score recompute
  24. 2026-07-22 22:09 UTCEG score recompute
  25. 2026-07-22 14:04 UTCEPSS rescore
Show 41 more
  1. 2026-07-22 14:04 UTCEPSS rescore
  2. 2026-07-20 17:04 UTCEPSS rescore
  3. 2026-07-15 16:54 UTCEPSS rescore
  4. 2026-07-12 05:43 UTCEPSS rescore
  5. 2026-07-12 04:52 UTCOSV refresh
  6. 2026-07-05 02:27 UTCEPSS rescore
  7. 2026-07-02 16:54 UTCEPSS rescore
  8. 2026-06-28 04:53 UTCEPSS rescore
  9. 2026-06-24 14:02 UTCEPSS rescore
  10. 2026-06-24 14:02 UTCEPSS rescore
  11. 2026-06-23 21:30 UTCEPSS rescore
  12. 2026-06-23 11:00 UTCOSV refresh
  13. 2026-06-21 14:54 UTCEPSS rescore
  14. 2026-06-21 14:54 UTCEPSS rescore
  15. 2026-06-17 17:50 UTCEPSS rescore
  16. 2026-06-15 17:45 UTCEPSS rescore
  17. 2026-06-13 22:57 UTCEPSS rescore
  18. 2026-06-12 23:09 UTCEPSS rescore
  19. 2026-06-10 22:15 UTCEPSS rescore
  20. 2026-06-06 12:40 UTCOSV refresh
  21. 2026-06-05 22:44 UTCEPSS rescore
  22. 2026-05-31 00:14 UTCEPSS rescore
  23. 2026-05-31 00:14 UTCEPSS rescore
  24. 2026-05-29 13:41 UTCEPSS rescore
  25. 2026-05-28 13:42 UTCEPSS rescore
  26. 2026-05-28 13:42 UTCEPSS rescore
  27. 2026-05-27 13:38 UTCEPSS rescore
  28. 2026-05-27 13:38 UTCEPSS rescore
  29. 2026-05-26 13:42 UTCEPSS rescore
  30. 2026-05-26 13:42 UTCEPSS rescore
  31. 2026-05-22 21:15 UTCEPSS rescore
  32. 2026-05-22 21:15 UTCEPSS rescore
  33. 2026-05-22 21:15 UTCEPSS rescore
  34. 2026-05-22 21:15 UTCEPSS rescore
  35. 2026-05-22 21:15 UTCEPSS rescore
  36. 2026-05-22 17:08 UTCEG score recompute
  37. 2026-05-22 17:08 UTCGHSA enrichment
  38. 2026-05-20 22:37 UTCEPSS rescore
  39. 2026-05-20 22:37 UTCEPSS rescore
  40. 2026-05-20 22:37 UTCEPSS rescore
  41. 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-EXPLOIT
    First seen May 6, 2023

    A PoC exploit for CVE-2017-5487 - WordPress User Enumeration.

    Open source ↗
  • GitHub PoCpatilkr/wp-CVE-2017-5487-exploit
    First seen Apr 26, 2020

    WordPress CVE-2017-5487 Exploit in Python

    Open source ↗
  • GitHub PoCGeunSam2/CVE-2017-5487
    First seen Jun 10, 2019

    POC of CVE-2017-5487 + tool

    Open source ↗
  • Exploit-DBEDB-41497
    First seen Mar 3, 2017

    WordPress Core < 4.7.1 - Username Enumeration

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2017-5487?
CVE-2017-5487 is a critical vulnerability published on January 15, 2017. 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.
When was CVE-2017-5487 disclosed?
CVE-2017-5487 was first published in the National Vulnerability Database on January 15, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-5487 actively exploited?
CVE-2017-5487 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 87% probability of exploitation in the next 30 days, which ranks it in the top 0.3% of all scored CVEs.
What is the CVSS score of CVE-2017-5487?
CVE-2017-5487 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2017-5487?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-5487, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-5487

Explore →

Is Your Infrastructure Affected by CVE-2017-5487?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs