# CVE-2019-13181: Code injection in n/a

> CSV injection in the web UI allows attackers to execute arbitrary commands via malicious spreadsheet data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 16 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8rpj-mgcc-4hwx

## What is CVE-2019-13181?

CVE-2019-13181 is a medium-severity code injection vulnerability in n/a, published on 16 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A CSV injection vulnerability exists in the web UI of SolarWinds Serv-U FTP Server v15.1.7.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

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

It affects 1 product.


Products: Solarwinds Serv-U Ftp Server.

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

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

## Is CVE-2019-13181 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15541](https://insights.sbomify.com/CVE-2020-15541/): Command injection in n/a (critical 9.8)
- [CVE-2020-15542](https://insights.sbomify.com/CVE-2020-15542/): Other in n/a (critical 9.8)
- [CVE-2020-15543](https://insights.sbomify.com/CVE-2020-15543/): Path traversal in n/a (critical 9.8)
- [CVE-2019-12181](https://insights.sbomify.com/CVE-2019-12181/): Command injection in n/a (high 8.8)
- [CVE-2018-19999](https://insights.sbomify.com/CVE-2018-19999/): Auth bypass in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13181 is a medium-severity code injection vulnerability in n/a, published on 16 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13181 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-2019-13181/ (Markdown: https://insights.sbomify.com/CVE-2019-13181/index.md)
```

## Sources

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

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