# CVE-2017-9846: Path traversal in n/a

> Authenticated attackers can exploit directory traversal in Winmail Server to move PHP files into web directories, achieving remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h6gg-6vf7-hrjf

## What is CVE-2017-9846?

CVE-2017-9846 is a high-severity path traversal vulnerability in n/a, published on 24 Jun 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Winmail Server 6.1 allows remote code execution by authenticated users who leverage directory traversal in a netdisk.php move_folder_file call to move a .php file from the FTP folder into a web folder.

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

## Which versions are affected by CVE-2017-9846?

It affects 1 product.


Products: Magicwinmail Winmail Server.

## How do I fix CVE-2017-9846?

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

## Is CVE-2017-9846 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-5700](https://insights.sbomify.com/CVE-2018-5700/): Path traversal in n/a (high 8.8)
- [CVE-2024-55492](https://insights.sbomify.com/CVE-2024-55492/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9846 and fix it if it is affected.

What it is: CVE-2017-9846 is a high-severity path traversal vulnerability in n/a, published on 24 Jun 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9846 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-2017-9846/ (Markdown: https://insights.sbomify.com/CVE-2017-9846/index.md)
```

## Sources

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

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