# CVE-2014-2069: Path traversal in n/a

> Remote attackers can read arbitrary files on the server by exploiting a path traversal vulnerability in the file manager component.

- **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:** 13 Apr 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8v54-89gr-p9gq

## What is CVE-2014-2069?

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

### Official description

Absolute path traversal vulnerability in Eshtery CMS allows remote attackers to read arbitrary files via a full pathname in the file parameter to FileManager.aspx.

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

## Which versions are affected by CVE-2014-2069?

It affects 1 product.


Products: Eshtery.she7ata Eshtery Cms.

## How do I fix CVE-2014-2069?

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

## Is CVE-2014-2069 being exploited?

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

Public exploit code:

- eshtery CMS - 'FileManager.aspx' Local File Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-3404](https://insights.sbomify.com/CVE-2010-3404/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2069 and fix it if it is affected.

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

## Sources

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

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