CVE-2017-1001000

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 82%
CISA-KEV: Not listedEPSS: 82%CVSS: 7.5Exploit: NoneExposed: 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
7.5(medium)
EPSS
99.6%
KEV
Not listed

Published

April 3, 2017

Last Modified

May 13, 2026

References (18)

Data Freshness Timeline

(refreshed 2× 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-07-04 06:28 UTCEPSS rescore
  2. 2026-07-01 15:02 UTCEPSS rescore
  3. 2026-06-25 13:47 UTCEPSS rescore
  4. 2026-06-24 14:02 UTCEPSS rescore
  5. 2026-06-23 21:30 UTCEPSS rescore
  6. 2026-06-23 07:30 UTCOSV refresh
  7. 2026-06-21 01:57 UTCEPSS rescore
  8. 2026-06-21 01:57 UTCEPSS rescore
  9. 2026-06-17 17:50 UTCEPSS rescore
  10. 2026-06-17 17:50 UTCEPSS rescore
  11. 2026-06-15 17:45 UTCEPSS rescore
  12. 2026-06-12 23:09 UTCEPSS rescore
  13. 2026-06-07 15:22 UTCEPSS rescore
  14. 2026-06-07 15:22 UTCEPSS rescore
  15. 2026-06-06 13:45 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-06 06:30 UTCOSV refresh
  18. 2026-06-05 06:08 UTCEPSS rescore
  19. 2026-06-05 06:08 UTCEPSS rescore
  20. 2026-06-04 13:10 UTCEPSS rescore
  21. 2026-06-04 13:10 UTCEPSS rescore
  22. 2026-06-01 13:49 UTCEPSS rescore
  23. 2026-06-01 13:49 UTCEPSS rescore
  24. 2026-05-31 22:28 UTCEPSS rescore
  25. 2026-05-31 22:28 UTCEPSS rescore
Show 15 more
  1. 2026-05-31 00:14 UTCEPSS rescore
  2. 2026-05-29 13:41 UTCEPSS rescore
  3. 2026-05-28 13:42 UTCEPSS rescore
  4. 2026-05-28 13:42 UTCEPSS rescore
  5. 2026-05-22 21:15 UTCEPSS rescore
  6. 2026-05-22 14:43 UTCEG score recompute
  7. 2026-05-22 14:42 UTCGHSA enrichment
  8. 2026-05-20 22:37 UTCEPSS rescore
  9. 2026-05-20 22:37 UTCEPSS rescore
  10. 2026-05-20 22:37 UTCEPSS rescore
  11. 2026-05-20 11:21 UTCEPSS rescore
  12. 2026-05-20 11:21 UTCEPSS rescore
  13. 2026-05-18 21:30 UTCEPSS rescore
  14. 2026-05-18 21:30 UTCEPSS rescore
  15. 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 May 13, 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 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-1001000?
CVE-2017-1001000 has a CVSS v3 base score of 7.5 (NVD).
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

Explore the affected products and dependency analysis for 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