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: 2017-04-02 Last update: 2026-06-16 Assigner: 46fe6300-5254-4a98-9594-a9567bec8179 Source: 46fe6300-5254-4a98-9594-a9567bec8179
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-1001000 is rated High Risk (67.8/100): CVSS High severity, with high exploitation likelihood (EPSS 81.85%, 100th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +2.91% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-1001000

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 78.93% 81.85% +2.91%
2 2026-03-23 80.37% 78.93% -1.44%
3 2025-12-28 — 80.37% —

Full EPSS history (20 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-1001000

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2017-1001000

OS Trackers for CVE-2017-1001000

vendor priority summary link
debian not yet assigned CVE-2017-1001000 not yet assigned priority: Debian including 1 source packages (wordpress), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-1001000
ubuntu medium CVE-2017-1001000 medium priority: Ubuntu including 1 source packages (wordpress), 5 status rows across 5 suites (precise, trusty, upstream, xenial, yakkety): not-affected 3, DNE 1, released 1. https://ubuntu.com/security/CVE-2017-1001000

Affected software / configurations for CVE-2017-1001000

Vendor Product Version Raw CPE
wordpress wordpress 4.7 cpe:2.3:a:wordpress:wordpress:4.7:*:*:*:*:*:*:*
wordpress wordpress 4.7.1 cpe:2.3:a:wordpress:wordpress:4.7.1:*:*:*:*:*:*:*
wordpress wordpress 4.7.2 cpe:2.3:a:wordpress:wordpress:4.7.2:*:*:*:*:*:*:*

References for CVE-2017-1001000

cvelogic Threat Intelligence