# CVE-2018-6008: Path traversal in n/a

> Attackers can download arbitrary files from the server via the download_file parameter in the Jtag Members Directory plugin.

- **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:** 29 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m48p-94mp-44pv

## What is CVE-2018-6008?

CVE-2018-6008 is a high-severity path traversal vulnerability in n/a, published on 29 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Arbitrary File Download exists in the Jtag Members Directory 5.3.7 component for Joomla! via the download_file parameter.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-6008?

It affects 1 product.


Products: Joomlatag Jtag Members Directory.

## How do I fix CVE-2018-6008?

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

## Is CVE-2018-6008 being exploited?

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

Public exploit code:

- Joomla! Component Jtag Members Directory 5.3.7 - Arbitrary File Download (exploitdb)
- Joomla! Jtag Members Directory 5.3.7 - Local File Inclusion (nuclei): http/cves/2018/CVE-2018-6008.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6008 and fix it if it is affected.

What it is: CVE-2018-6008 is a high-severity path traversal vulnerability in n/a, published on 29 Jan 2018. 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-2018-6008 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-2018-6008/ (Markdown: https://insights.sbomify.com/CVE-2018-6008/index.md)
```

## Sources

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

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