# CVE-2019-9858: Path traversal in n/a

> Attackers can exploit path traversal in image upload handling to write PHP backdoors to the web root, 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:** Yes
- **Published:** 29 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-9858, DLA-1822-1, DSA-4468-1, GHSA-mhgr-3vxf-9f79, UBUNTU-CVE-2019-9858

## What is CVE-2019-9858?

CVE-2019-9858 is a high-severity path traversal vulnerability in Debian Debian Linux, published on 29 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Remote code execution was discovered in Horde Groupware Webmail 5.2.22 and 5.2.17. Horde/Form/Type.php contains a vulnerable class that handles image upload in forms. When the Horde_Form_Type_image method onSubmit() is called on uploads, it invokes the functions getImage() and _getUpload(), which uses unsanitized user input as a path to save the image. The unsanitized POST parameter object[photo][img][file] is saved in the $upload[img][file] PHP variable, allowing an attacker to manipulate the $tmp_file passed to move_uploaded_file() to save the uploaded file. By setting the parameter to (for example) ../usr/share/horde/static/bd.php, one can write a PHP backdoor inside the web root. The static/ destination folder is a good candidate to drop the backdoor because it is always writable in Horde installations. (The unsanitized POST parameter went probably unnoticed because it's never submitted by the forms, which default to securely using a random path.)

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

## Which versions are affected by CVE-2019-9858?

It affects 2 products.


Products: Debian Debian Linux, Horde Groupware.

## How do I fix CVE-2019-9858?

Apply the vendor's patch.

## Is CVE-2019-9858 being exploited?

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

Public exploit code:

- Horde Form File Upload Vulnerability (metasploit)

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9858 and fix it if it is affected.

What it is: CVE-2019-9858 is a high-severity path traversal vulnerability in Debian Debian Linux, published on 29 May 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-9858 exists.

Affected product: Debian Debian Linux. 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-2019-9858/ (Markdown: https://insights.sbomify.com/CVE-2019-9858/index.md)
```

## Sources

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

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