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

> Attackers can achieve remote code execution in Bludit by uploading malicious PHP code disguised as images and writing it to arbitrary paths.

- **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:** 8 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-ch69-hjrw-4hf3

## What is CVE-2019-16113?

CVE-2019-16113 is a high-severity path traversal vulnerability in n/a, published on 8 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Bludit 3.9.2 allows remote code execution via bl-kernel/ajax/upload-images.php because PHP code can be entered with a .jpg file name, and then this PHP code can write other PHP code to a ../ pathname.

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

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

It affects 1 product.


Products: Bludit Bludit.

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

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

## Is CVE-2019-16113 being exploited?

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

Public exploit code:

- CVE-2019-16113  - bludit >= 3.9.2 RCE authenticate (github_poc): https://github.com/cybervaca/CVE-2019-16113
- https://github.com/ynots0ups/CVE-2019-16113 (github_poc): https://github.com/ynots0ups/CVE-2019-16113
- Bludit >= 3.9.2 - Authenticated RCE (CVE-2019-16113) (github_poc): https://github.com/hg8/CVE-2019-16113-PoC
- Bludit 3.9.2 Remote Command Execution (RCE) (github_poc): https://github.com/mind2hex/CVE-2019-16113-Bludit-3.9.2-RCE
- Bludit Directory Traversal Image File Upload Vulnerability (metasploit)
- Bludit - Directory Traversal Image File Upload (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-18879](https://insights.sbomify.com/CVE-2020-18879/): File upload in n/a (critical 9.8)
- [CVE-2020-20495](https://insights.sbomify.com/CVE-2020-20495/): Path traversal in n/a (critical 9.1)
- [CVE-2020-18190](https://insights.sbomify.com/CVE-2020-18190/): Path traversal in n/a (critical 9.1)
- [CVE-2024-24550](https://insights.sbomify.com/CVE-2024-24550/): Bludit - Remote Code Execution (RCE) through File API (high 8.9)
- [CVE-2024-24551](https://insights.sbomify.com/CVE-2024-24551/): Bludit - Remote Code Execution (RCE) through Image API (high 8.9)

## Fix prompt for AI coding agents

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

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

## Sources

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

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