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

> Remote attackers can retrieve arbitrary files from the server via a Local File Inclusion vulnerability in the Nevma Adaptive Images plugin.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 21 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5mh3-8c2p-hgm8

## What is CVE-2019-14205?

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

### Official description

A Local File Inclusion vulnerability in the Nevma Adaptive Images plugin before 0.6.67 for WordPress allows remote attackers to retrieve arbitrary files via the $REQUEST['adaptive-images-settings']['source_file'] parameter in adaptive-images-script.php.

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

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

It affects 1 product.


Products: Nevma Adaptive Images.

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

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

## Is CVE-2019-14205 being exploited?

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

Public exploit code:

- WordPress Nevma Adaptive Images <0.6.67 - Local File Inclusion (nuclei): http/cves/2019/CVE-2019-14205.yaml

## Other vulnerabilities in n/a

- [CVE-2019-14206](https://insights.sbomify.com/CVE-2019-14206/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14205 is a high-severity path traversal vulnerability in n/a, published on 21 Jul 2019. 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-2019-14205 exists.

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

## Sources

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

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