# CVE-2015-1876: Path traversal in n/a

> Attackers can exploit a directory traversal flaw in ES File Explorer to read or modify arbitrary files on the device.

- **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:** 28 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fhgq-r82x-93wr

## What is CVE-2015-1876?

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

### Official description

Directory traversal vulnerability in ES File Explorer 3.2.4.1.

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

## Which versions are affected by CVE-2015-1876?

It affects 1 product.


Products: Estrongs Es File Explorer.

## How do I fix CVE-2015-1876?

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

## Is CVE-2015-1876 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-1970](https://insights.sbomify.com/CVE-2014-1970/): Path traversal in n/a (medium 5.8)
- [CVE-2012-0322](https://insights.sbomify.com/CVE-2012-0322/): Missing authorization in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1876 and fix it if it is affected.

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

## Sources

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

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