Vulnerability in WordPress

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 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.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 7.5 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

EPSS exploit prediction

EPSS: 0.849 (99.7th percentile), scored .

High probability of exploitation in the next 30 days — patch promptly. 100th percentile — 99.7% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2017-1001000: held from 0.849 to 0.849.

EPSS over last 30 days · oldest: 0.849 · newest: 0.849 · change: 0.000

Affected products

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2017-1001000?
CVE-2017-1001000 is a high-severity vulnerability in WordPress. CVSS score: 7.5/10. Published 2017-04-03.
How severe is CVE-2017-1001000?
High severity. CVSS v3 base score is 7.5 out of 10.
Is CVE-2017-1001000 known to be exploited?
14 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.