WordPress component: A security weakness
WordPress component is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- WordPress component
- Plugin slug
Core- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Apr 03, 2017
- Weakness
- NVD-CWE-noinfo
This CVE was published Apr 03, 2017 and is one of 45 known issues for WordPress core.
Patch or disable the affected component.
Update WordPress component to a release outside the affected range, or disable and remove it until a fixed version is available.
Technical 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.
NVD vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Primary and upstream sources
- NVD record for CVE-2017-1001000
- Upstream reference openwall.com
- Upstream reference securitytracker.com
- Upstream reference blog.sucuri.net
- Upstream reference blogs.akamai.com
- WordPress upstream reference codex.wordpress.org
- Upstream reference gist.github.com
- GitHub upstream reference github.com
- WordPress upstream reference make.wordpress.org
- WordPress upstream reference wordpress.org
- Upstream reference openwall.com
- Upstream reference securitytracker.com
- Upstream reference blog.sucuri.net
- Upstream reference blogs.akamai.com
- WordPress upstream reference codex.wordpress.org
- Upstream reference gist.github.com
- GitHub upstream reference github.com
- WordPress upstream reference make.wordpress.org
- WordPress upstream reference wordpress.org