# CVE-2018-9107: Other in n/a

> Attackers can inject malicious formulas into CSV exports, potentially leading to code execution when the file is opened in spreadsheet software.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rcxm-j6w4-fgvv

## What is CVE-2018-9107?

CVE-2018-9107 is a high-severity vulnerability in n/a, published on 28 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

CSV Injection (aka Excel Macro Injection or Formula Injection) exists in the export feature in the Acyba AcyMailing extension before 5.9.6 for Joomla! via a value that is mishandled in a CSV export.

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

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

It affects 1 product.


Products: Acyba Acymailing.

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

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

## Is CVE-2018-9107 being exploited?

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

Public exploit code:

- Joomla! Component Acymailing Starter 5.9.5 - CSV Macro Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2020-10934](https://insights.sbomify.com/CVE-2020-10934/): File upload in n/a (high 7.2)
- [CVE-2015-7338](https://insights.sbomify.com/CVE-2015-7338/): SQL injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-9107 is a high-severity vulnerability in n/a, published on 28 Mar 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-9107 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-2018-9107/ (Markdown: https://insights.sbomify.com/CVE-2018-9107/index.md)
```

## Sources

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

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