WordPress security changelog
HIGH CVE-2017-1001000 Deferred

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.

CVE / CNA score Pending The CVE record has not published a CNA CVSS assessment.
NVD score 7.5 CVSS 3.0 · nvd@nist.gov
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 47 known issues for WordPress core.

Update, patch or deactivate.

No fixed release is identified. Update WordPress component when a confirmed fixed release becomes available; until then, disable and remove it when the site's risk warrants.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

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