# CVE-2017-1001000: Missing authorization in n/a

> Remote attackers can modify arbitrary pages by exploiting improper input validation in the WordPress REST API endpoints.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-1001000, GHSA-qm68-r9p4-ghhx

## What is CVE-2017-1001000?

CVE-2017-1001000 is a high-severity missing authorization vulnerability in Wordpress Wordpress, published on 3 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

## Which versions are affected by CVE-2017-1001000?

It affects 1 product.


Products: Wordpress Wordpress.

## How do I fix CVE-2017-1001000?

Upgrade to a fixed version.

## Is CVE-2017-1001000 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-1001000 exists.

Public exploit code:

- WordPress REST API Content Injection (metasploit)

## Other vulnerabilities in Wordpress Wordpress

- [CVE-2026-63030](https://insights.sbomify.com/CVE-2026-63030/): WordPress Core Interpretation Conflict (critical 9.8, exploited in the wild)
- [CVE-2026-87902](https://insights.sbomify.com/CVE-2026-87902/): WordPress Core Remote File Inclusion (high 8.1, exploited in the wild)
- [CVE-2026-60137](https://insights.sbomify.com/CVE-2026-60137/): WordPress Core SQL Injection (medium 5.9, exploited in the wild)
- [CVE-2012-2399](https://insights.sbomify.com/CVE-2012-2399/): Cross-site scripting in n/a (critical 10.0)
- [CVE-2012-2400](https://insights.sbomify.com/CVE-2012-2400/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1001000 and fix it if it is affected.

What it is: CVE-2017-1001000 is a high-severity missing authorization vulnerability in Wordpress Wordpress, published on 3 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-1001000 exists.

Affected product: Wordpress Wordpress. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-1001000/ (Markdown: https://insights.sbomify.com/CVE-2017-1001000/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-1001000
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-1001000
- OSV: https://osv.dev/vulnerability/CVE-2017-1001000

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-1001000/
Summaries are generated and may contain mistakes; the official description above is the record.