CVE-2017-1001000
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data tampering.
- Exploit odds
- 84.9% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 84.9% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 84.9% · EPSS, next 30 days
- Record status
- Modified
Affected
- WordPress 4.7
- WordPress 4.7.1
- WordPress 4.7.2
Attack profile CVSS 3.0 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-1001000.md and follow it. Check whether this project is affected by CVE-2017-1001000. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/WordPress/WordPress/commit/e357195ce303017d517aff944644a7a1232926f7
- https://github.com/WordPress/WordPress/commit/e357195ce303017d517aff944644a7a1232926f7
References
- http://www.openwall.com/lists/oss-security/2017/02/10/16
- http://www.securitytracker.com/id/1037731
- https://blog.sucuri.net/2017/02/content-injection-vulnerability-wordpress-rest-api.html
- https://blogs.akamai.com/2017/02/wordpress-web-api-vulnerability.html
- https://codex.wordpress.org/Version_4.7.2
- https://gist.github.com/leonjza/2244eb15510a0687ed93160c623762ab
- https://github.com/WordPress/WordPress/commit/e357195ce303017d517aff944644a7a1232926f7
- https://make.wordpress.org/core/2017/02/01/disclosure-of-additional-security-fix-in-wordpress-4-7-2/
- https://wordpress.org/news/2017/01/wordpress-4-7-2-security-release/
- http://www.openwall.com/lists/oss-security/2017/02/10/16
- http://www.securitytracker.com/id/1037731
- https://blog.sucuri.net/2017/02/content-injection-vulnerability-wordpress-rest-api.html
- https://blogs.akamai.com/2017/02/wordpress-web-api-vulnerability.html
- https://codex.wordpress.org/Version_4.7.2
- https://gist.github.com/leonjza/2244eb15510a0687ed93160c623762ab
- https://github.com/WordPress/WordPress/commit/e357195ce303017d517aff944644a7a1232926f7
- https://make.wordpress.org/core/2017/02/01/disclosure-of-additional-security-fix-in-wordpress-4-7-2/
- https://wordpress.org/news/2017/01/wordpress-4-7-2-security-release/