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

> Attackers can read arbitrary files via directory traversal in the template editor, exposing sensitive data in Lei Feng TV CMS.

- **Severity:** Medium 4.9 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Dec 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vq7x-jpfh-39f4

## What is CVE-2018-20604?

CVE-2018-20604 is a medium-severity path traversal vulnerability in n/a, published on 30 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Lei Feng TV CMS (aka LFCMS) 3.8.6 allows Directory Traversal via crafted use of ..* in Template/edit/path URIs, as demonstrated by the admin.php?s=/Template/edit/path/*web*..*..*..*..*1.txt.html URI to read the 1.txt file.

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

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

It affects 1 product.


Products: Lfdycms Lei Feng Tv Cms.

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

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

## Is CVE-2018-20604 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-20603](https://insights.sbomify.com/CVE-2018-20603/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-20602](https://insights.sbomify.com/CVE-2018-20602/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20604 is a medium-severity path traversal vulnerability in n/a, published on 30 Dec 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20604 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-2018-20604/ (Markdown: https://insights.sbomify.com/CVE-2018-20604/index.md)
```

## Sources

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

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