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

> An attacker can exploit directory traversal in Responsive FileManager to read or modify files outside the restricted directory.

- **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:** 24 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h224-3vc9-hqhf

## What is CVE-2018-15535?

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

### Official description

/filemanager/ajax_calls.php in tecrail Responsive FileManager before 9.13.4 uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize get_file sequences such as ".." that can resolve to a location that is outside of that directory, aka Directory Traversal.

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

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

It affects 1 product.


Products: Tecrail Responsive Filemanager.

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

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

## Is CVE-2018-15535 being exploited?

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

Public exploit code:

- Responsive FileManager < 9.13.4 - Directory Traversal (exploitdb)
- Responsive FileManager <9.13.4 - Local File Inclusion (nuclei): http/cves/2018/CVE-2018-15535.yaml

## Other vulnerabilities in n/a

- [CVE-2022-44276](https://insights.sbomify.com/CVE-2022-44276/): File upload in n/a (critical 9.8)
- [CVE-2020-10567](https://insights.sbomify.com/CVE-2020-10567/): File upload in n/a (critical 9.8)
- [CVE-2020-10212](https://insights.sbomify.com/CVE-2020-10212/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2018-14728](https://insights.sbomify.com/CVE-2018-14728/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2022-46604](https://insights.sbomify.com/CVE-2022-46604/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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