# CVE-2018-11526: Code injection in n/a

> CSV injection in WordPress Comments Import & Export plugin allows attackers to execute arbitrary code via crafted CSV files.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c2pm-8q3x-vjgf

## What is CVE-2018-11526?

CVE-2018-11526 is a high-severity code injection vulnerability in n/a, published on 19 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The plugin "WordPress Comments Import & Export" for WordPress (v2.0.4 and before) is vulnerable to CSV Injection.

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

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

It affects 1 product.


Products: Webtoffee Wordpress Comments Import and Export.

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

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

## Is CVE-2018-11526 being exploited?

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

Public exploit code:

- WordPress Plugin Comments Import & Export < 2.0.4 - CSV Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2022-45370](https://insights.sbomify.com/CVE-2022-45370/): WordPress WordPress Comments Import & Export Plugin <= 2.3.1 is vulnerable to CSV Injection (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-11526 is a high-severity code injection vulnerability in n/a, published on 19 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-11526 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-11526/ (Markdown: https://insights.sbomify.com/CVE-2018-11526/index.md)
```

## Sources

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

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