# CVE-2017-14719: Path traversal in n/a

> Attackers can exploit directory traversal in WordPress unzip operations to read or modify arbitrary files on the server.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 23 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-14719, GHSA-8rmg-wmq4-q93v, UBUNTU-CVE-2017-14719

## What is CVE-2017-14719?

CVE-2017-14719 is a high-severity path traversal vulnerability in Wordpress Wordpress, published on 23 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Before version 4.8.2, WordPress was vulnerable to a directory traversal attack during unzip operations in the ZipArchive and PclZip components.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Wordpress Wordpress.

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

Upgrade to a fixed version.

## Is CVE-2017-14719 being exploited?

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

Public exploit code:

- CodePath Assignment for Weeks 7 & 8: CVE-2017-14719, CVE-2019-9787 & Unauthenticated Page/Post Content Modification via REST API (github_poc): https://github.com/PalmTreeForest/CodePath_Week_7-8

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

What it is: CVE-2017-14719 is a high-severity path traversal vulnerability in Wordpress Wordpress, published on 23 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14719 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-14719/ (Markdown: https://insights.sbomify.com/CVE-2017-14719/index.md)
```

## Sources

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

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