CVE-2017-1001000 in the critical feed json
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…
published 9y ago modified 4mo ago also EUVD-2017-1613
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 84.9%
- EPSS 84.9% chance of exploitation in 30 days, percentile 99.7%
- public exploits
- 1
- Metasploit
Summary
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.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 4.7.2+dfsg-1
debian advisories DEBIAN-CVE-2017-1001000
Is CVE-2017-1001000 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 FencerTimeline
- First public exploit (Metasploit auxiliary/scanner/http/wordpress_content_injection)
- Published
Exploit prediction
84.94% chance of exploitation in the next 30 days, higher than 99.7% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit auxiliary/scanner/http/wordpress_content_injection WordPress REST API Content Injection metasploit auxiliary, normal rank, 2017-02-01
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Technology feeds
References
- github.com /WordPress/WordPress/commit/e357195ce303017d517aff944644a7a1232926f7
- codex.wordpress.org /Version_4.7.2
- make.wordpress.org /core/2017/02/01/disclosure-of-additional-security-fix-in-wordpress-4-7-2/
- blogs.akamai.com /2017/02/wordpress-web-api-vulnerability.html
- gist.github.com /leonjza/2244eb15510a0687ed93160c623762ab
- blog.sucuri.net /2017/02/content-injection-vulnerability-wordpress-rest-api.html
- wordpress.org /news/2017/01/wordpress-4-7-2-security-release/
-
openwall.com
/lists/oss-security/2017/02/10/16
mailing-list
-
securitytracker.com
/id/1037731
vdb-entry
Sources
- CVE List CVE-2017-1001000
- NVD CVE-2017-1001000
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.