# CVE-2022-1539: Exports and Reports < 0.9.2 - Contributor+ CSV Injection

> Contributors can inject malicious formulas into CSV exports, potentially executing code or leaking data when opened in Excel.

- **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:** 25 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-x6c4-gw3r-222g

## What is CVE-2022-1539?

CVE-2022-1539 is a high-severity vulnerability in Unknown Exports and Reports, published on 25 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Exports and Reports WordPress plugin before 0.9.2 does not sanitize and validate data when generating the CSV to export, which could lead to a CSV injection, by the use of Microsoft Excel DDE function, or to leak data via maliciously injected hyperlinks.

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

## Which versions are affected by CVE-2022-1539?

It affects 1 product.


Products: Exports and Reports Project Exports and Reports.

## How do I fix CVE-2022-1539?

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

## Is CVE-2022-1539 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1539 and fix it if it is affected.

What it is: CVE-2022-1539 is a high-severity vulnerability in Unknown Exports and Reports, published on 25 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1539 in the wild and no public exploit code.

Affected product: Unknown Exports and Reports. 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-2022-1539/ (Markdown: https://insights.sbomify.com/CVE-2022-1539/index.md)
```

## Sources

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

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