CVE-2017-1001000
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…
- 7.5HighCVSS base score
- 84.9%Exploitation in 30 daysEPSS · top 0.3% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- 1Public exploitsMetasploit, Nuclei and Exploit-DB
Description
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.
Public exploit
An exploit or proof of concept is public: anyone can try it against an unpatched system. The public collections list a Metasploit module for it.
Show the exploits1
Metasploit modules1 module
- WordPress REST API Content Injection (Metasploit module) (opens in a new tab)
auxiliary/scanner/http/wordpress_content_injectionRank normaldisclosed 1 Feb 2017
Modules, templates and exploits as listed by the Metasploit Framework (BSD-3-Clause), ProjectDiscovery's Nuclei templates (MIT) and the Exploit Database (GPLv2), read once a day. Where the data comes from
Timeline
ID reserved
By joshbressers
- 1 day later
· 1 day later
Published
- 7 years later
· 7 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.0 | High7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
- EPSS (exploitation in 30 days)
- 84.9% · top 0.3% of all CVEs (11 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.
Affected products
n/a
- affected n/a
References
References9
- https://codex.wordpress.org/Version_4.7.2 (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://make.wordpress.org/core/2017/02/01/disclosure-of-additional-security-fix-in-wordpress-4-7-2/ (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://blogs.akamai.com/2017/02/wordpress-web-api-vulnerability.html (opens in a new tab)x_refsource_MISCx_transferred
- https://gist.github.com/leonjza/2244eb15510a0687ed93160c623762ab (opens in a new tab)x_refsource_MISCx_transferred
- https://blog.sucuri.net/2017/02/content-injection-vulnerability-wordpress-rest-api.html (opens in a new tab)x_refsource_MISCx_transferred
- https://github.com/WordPress/WordPress/commit/e357195ce303017d517aff944644a7a1232926f7 (opens in a new tab)x_refsource_CONFIRMx_transferred
- https://wordpress.org/news/2017/01/wordpress-4-7-2-security-release/ (opens in a new tab)x_refsource_CONFIRMx_transferred
- [oss-security] 20170210 Re: Asking for a CVE id for the WordPress Privilege Escalation vulnerability (4.7/4.7.1) (opens in a new tab)mailing-listx_refsource_MLISTx_transferred
- 1037731 (opens in a new tab)vdb-entryx_refsource_SECTRACKx_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2017-1613 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2017-1001000)Record last updated .