# CVE-2022-3574: WPForms Pro < 1.7.7 - CSV Injection

> An attacker can inject malicious formulas into exported CSV files, potentially leading to code execution when the file is opened in spreadsheet software.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-6mxj-jjjj-8mpv

## What is CVE-2022-3574?

CVE-2022-3574 is a critical vulnerability in Unknown WPForms Pro, published on 14 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WPForms Pro WordPress plugin before 1.7.7 does not validate its form data when generating the exported CSV, which could lead to CSV injection.

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

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

It affects 1 product.


Products: Wpforms Wpforms Pro.

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

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

## Is CVE-2022-3574 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3574 is a critical vulnerability in Unknown WPForms Pro, published on 14 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3574 exists.

Affected product: Unknown WPForms Pro. 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-3574/ (Markdown: https://insights.sbomify.com/CVE-2022-3574/index.md)
```

## Sources

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

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