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

> Remote attackers can inject malicious spreadsheet formulas into CSV exports via the contact form, potentially leading to code execution when files are opened.

- **Severity:** Critical 9.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/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:** 4 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jvg2-rvxj-jmp7

## What is CVE-2018-9035?

CVE-2018-9035 is a critical vulnerability in n/a, published on 4 Apr 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 vulnerability in ExportToCsvUtf8.php of the Contact Form 7 to Database Extension plugin 2.10.32 for WordPress allows remote attackers to inject spreadsheet formulas into CSV files via the contact form.

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

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

It affects 1 product.


Products: Contact-Form-7-to-Database-Extension Project Contact-Form-7-to-Database-Extension.

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

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

## Is CVE-2018-9035 being exploited?

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

Public exploit code:

- WordPress Plugin Contact Form 7 to Database Extension 2.10.32 - CSV Injection (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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