# CVE-2020-22276: Other in n/a

> Attackers can inject malicious formulas into CSV exports via WeForms entries, potentially leading to code execution when 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:** 4 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mpjr-7qj2-46x4

## What is CVE-2020-22276?

CVE-2020-22276 is a critical vulnerability in n/a, published on 4 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WeForms Wordpress Plugin 1.4.7 allows CSV injection via a form's entry.

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

## Which versions are affected by CVE-2020-22276?

It affects 1 product.


Products: Weformspro Weforms.

## How do I fix CVE-2020-22276?

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

## Is CVE-2020-22276 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-0386](https://insights.sbomify.com/CVE-2024-0386/): weForms <= 1.6.21 - Unauthenticated Stored Cross-Site Scripting via Referer (high 7.2)
- [CVE-2023-50896](https://insights.sbomify.com/CVE-2023-50896/): WordPress weForms Plugin <= 1.6.17 is vulnerable to Cross Site Scripting (XSS) (medium 5.9)
- [CVE-2022-2395](https://insights.sbomify.com/CVE-2022-2395/): weForms < 1.6.14 - Admin+ Stored Cross-Site Scripting (medium 4.8)
- [CVE-2023-51524](https://insights.sbomify.com/CVE-2023-51524/): WordPress weForms plugin <= 1.6.18 - Broken Access Control vulnerability (medium 4.3)
- [CVE-2024-30512](https://insights.sbomify.com/CVE-2024-30512/): WordPress weForms plugin <= 1.6.20 - Broken Access Control vulnerability (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-22276 and fix it if it is affected.

What it is: CVE-2020-22276 is a critical vulnerability in n/a, published on 4 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-22276 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-2020-22276/ (Markdown: https://insights.sbomify.com/CVE-2020-22276/index.md)
```

## Sources

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

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