# CVE-2017-1000600: WordPress version <4.9 contains a CWE-20 Input Validation vulnerability in thumbnail processing that can result in remote code execution.


- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 6 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-1000600, GHSA-38pv-q5j7-w3w9, UBUNTU-CVE-2017-1000600

## What is CVE-2017-1000600?

CVE-2017-1000600 is a high-severity vulnerability in Wordpress Wordpress, published on 6 Sep 2018. 

### Official description

WordPress version <4.9 contains a CWE-20 Input Validation vulnerability in thumbnail processing that can result in remote code execution. This attack appears to be exploitable via thumbnail upload by an authenticated user and may require additional plugins in order to be exploited however this has not been confirmed at this time. This issue appears to have been partially, but not completely fixed in WordPress 4.9

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Wordpress Wordpress.

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

Upgrade to a fixed version.

## Is CVE-2017-1000600 being exploited?

There is no known exploitation of CVE-2017-1000600 in the wild and no public exploit code.

## 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-1000600 and fix it if it is affected.

What it is: CVE-2017-1000600 is a high-severity vulnerability in Wordpress Wordpress, published on 6 Sep 2018. 
Exploitation: There is no known exploitation of CVE-2017-1000600 in the wild and no public exploit code.

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-1000600/ (Markdown: https://insights.sbomify.com/CVE-2017-1000600/index.md)
```

## Sources

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

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