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

> Low-privilege users can inject commands into exported CSV files, potentially leading to code execution on the client system.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 1 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mv4v-hhm3-2c3m

## What is CVE-2018-10255?

CVE-2018-10255 is a high-severity code injection vulnerability in n/a, published on 1 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A CSV Injection vulnerability was discovered in clustercoding Blog Master Pro v1.0 that allows a user with low level privileges to inject a command that will be included in the exported CSV file, leading to possible code execution.

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

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

It affects 1 product.


Products: Clustercoding Blog Master Pro.

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

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

## Is CVE-2018-10255 being exploited?

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

Public exploit code:

- Blog Master Pro 1.0 - CSV Injection (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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