CVE-2017-1001000

HIGHNVD 7.58.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.9 because EPSS predicts 82% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
8.9EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 85%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 85%CVSS: 7.5Exploit: Metasploit · epss top5pct · epss high · public exploitExposed: 0

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

The register_routes function in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in the REST API in WordPress 4.7.x before 4.7.2 does not require an integer identifier, which allows remote attackers to modify arbitrary pages via a request for wp-json/wp/v2/posts followed by a numeric value and a non-numeric value, as demonstrated by the wp-json/wp/v2/posts/123?id=123helloworld URI.

CVSS v3
7.5
EG Score
8.9(high)
EG Risk
77(Track)
EG Risk 77/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
Severity89% × 45%
Exploitation82% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
85%
EPSS %ILE
100%
KEV
Not listed

Published

April 3, 2017

Last Modified

June 17, 2026

References (18)

Affected Packages

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

Data Freshness Timeline

(refreshed 4× 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.

  1. 2026-08-19 16:59 UTCEPSS rescore
  2. 2026-08-18 13:43 UTCEPSS rescore
  3. 2026-08-16 14:51 UTCEPSS rescore
  4. 2026-08-16 02:10 UTCEPSS rescore
  5. 2026-08-15 01:25 UTCEPSS rescore
  6. 2026-08-14 03:49 UTCOSV refresh
  7. 2026-08-12 13:46 UTCEPSS rescore
  8. 2026-08-04 15:05 UTCEPSS rescore
  9. 2026-07-29 08:33 UTCOSV refresh
  10. 2026-07-26 14:50 UTCEPSS rescore
  11. 2026-07-24 14:13 UTCEPSS rescore
  12. 2026-07-23 14:15 UTCEPSS rescore
  13. 2026-07-23 01:25 UTCEG score recompute▲ 1.40
  14. 2026-07-22 22:04 UTCEG score recompute
  15. 2026-07-22 14:04 UTCEPSS rescore
  16. 2026-07-21 15:21 UTCEPSS rescore
  17. 2026-07-21 15:21 UTCEPSS rescore
  18. 2026-07-20 17:04 UTCEPSS rescore
  19. 2026-07-19 02:26 UTCEPSS rescore
  20. 2026-07-19 02:26 UTCEPSS rescore
  21. 2026-07-15 16:54 UTCEPSS rescore
  22. 2026-07-15 16:54 UTCEPSS rescore
  23. 2026-07-15 01:56 UTCEPSS rescore
  24. 2026-07-12 01:11 UTCOSV refresh
  25. 2026-07-11 08:24 UTCEPSS rescore
Show 41 more
  1. 2026-07-09 19:06 UTCEPSS rescore
  2. 2026-07-04 06:28 UTCEPSS rescore
  3. 2026-07-01 15:02 UTCEPSS rescore
  4. 2026-06-25 13:47 UTCEPSS rescore
  5. 2026-06-24 14:02 UTCEPSS rescore
  6. 2026-06-23 21:30 UTCEPSS rescore
  7. 2026-06-23 07:30 UTCOSV refresh
  8. 2026-06-21 01:57 UTCEPSS rescore
  9. 2026-06-21 01:57 UTCEPSS rescore
  10. 2026-06-17 17:50 UTCEPSS rescore
  11. 2026-06-17 17:50 UTCEPSS rescore
  12. 2026-06-15 17:45 UTCEPSS rescore
  13. 2026-06-12 23:09 UTCEPSS rescore
  14. 2026-06-07 15:22 UTCEPSS rescore
  15. 2026-06-07 15:22 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-06 13:45 UTCEPSS rescore
  18. 2026-06-06 06:30 UTCOSV refresh
  19. 2026-06-05 06:08 UTCEPSS rescore
  20. 2026-06-05 06:08 UTCEPSS rescore
  21. 2026-06-04 13:10 UTCEPSS rescore
  22. 2026-06-04 13:10 UTCEPSS rescore
  23. 2026-06-01 13:49 UTCEPSS rescore
  24. 2026-06-01 13:49 UTCEPSS rescore
  25. 2026-05-31 22:28 UTCEPSS rescore
  26. 2026-05-31 22:28 UTCEPSS rescore
  27. 2026-05-31 00:14 UTCEPSS rescore
  28. 2026-05-29 13:41 UTCEPSS rescore
  29. 2026-05-28 13:42 UTCEPSS rescore
  30. 2026-05-28 13:42 UTCEPSS rescore
  31. 2026-05-22 21:15 UTCEPSS rescore
  32. 2026-05-22 14:43 UTCEG score recompute
  33. 2026-05-22 14:42 UTCGHSA enrichment
  34. 2026-05-20 22:37 UTCEPSS rescore
  35. 2026-05-20 22:37 UTCEPSS rescore
  36. 2026-05-20 22:37 UTCEPSS rescore
  37. 2026-05-20 11:21 UTCEPSS rescore
  38. 2026-05-20 11:21 UTCEPSS rescore
  39. 2026-05-18 21:30 UTCEPSS rescore
  40. 2026-05-18 21:30 UTCEPSS rescore
  41. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitauxiliary/scanner/http/wordpress_content_injection✓ verified
    First seen Feb 1, 2017

    WordPress REST API Content Injection

    Open source ↗

Frequently asked(5)

What is CVE-2017-1001000?
CVE-2017-1001000 is a high vulnerability published on April 3, 2017. The register_routes function in wp-includes/rest-api/endpoints/class-wp-rest-posts-controller.php in the REST API in WordPress 4.7.x before 4.7.2 does not require an integer identifier, which allows remote attackers to modify arbitrary pages via a request for wp-json/wp/v2/posts followed by a…
When was CVE-2017-1001000 disclosed?
CVE-2017-1001000 was first published in the National Vulnerability Database on April 3, 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-1001000 actively exploited?
CVE-2017-1001000 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85% 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-1001000?
CVE-2017-1001000 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9.
How do I remediate CVE-2017-1001000?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-1001000, 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-1001000

Explore →

Is Your Infrastructure Affected by CVE-2017-1001000?

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

Start Free Scan →Browse All CVEs