# CVE-2018-9137: Open-AudIT before 2.2 has CSV Injection.


- **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4fc7-7qm8-3hr4

## What is CVE-2018-9137?

CVE-2018-9137 is a medium-severity vulnerability in n/a, published on 19 Apr 2018. 

### Official description

Open-AudIT before 2.2 has CSV Injection.

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

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

It affects 1 product.


Products: Open-Audit Open-Audit.

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

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

## Is CVE-2018-9137 being exploited?

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

Public exploit code:

- Open-AudIT 2.1 - CSV Macro Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-8979](https://insights.sbomify.com/CVE-2018-8979/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-8937](https://insights.sbomify.com/CVE-2018-8937/): Open redirect in n/a (medium 6.1)
- [CVE-2018-9155](https://insights.sbomify.com/CVE-2018-9155/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2018-8978](https://insights.sbomify.com/CVE-2018-8978/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2018-8903](https://insights.sbomify.com/CVE-2018-8903/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-9137 is a medium-severity vulnerability in n/a, published on 19 Apr 2018. 
Exploitation: There is no known exploitation of CVE-2018-9137 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-2018-9137/ (Markdown: https://insights.sbomify.com/CVE-2018-9137/index.md)
```

## Sources

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

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