# CVE-2019-15330: Path traversal in n/a

> An attacker can read arbitrary files from the server via the webp-express WordPress plugin due to insufficient protection against path traversal.

- **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:** No
- **Published:** 22 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hq9w-4h7q-x8qw

## What is CVE-2019-15330?

CVE-2019-15330 is a high-severity path traversal vulnerability in n/a, published on 22 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The webp-express plugin before 0.14.11 for WordPress has insufficient protection against arbitrary file reading.

## Which versions are affected by CVE-2019-15330?

It affects 1 product.


Products: Webp Express Project Webp Express.

## How do I fix CVE-2019-15330?

No fix has been published for CVE-2019-15330 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-15330 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15330 and fix it if it is affected.

What it is: CVE-2019-15330 is a high-severity path traversal vulnerability in n/a, published on 22 Aug 2019. 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-2019-15330 in the wild and no public exploit code.

Affected product: n/a. 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-2019-15330/ (Markdown: https://insights.sbomify.com/CVE-2019-15330/index.md)
```

## Sources

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

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