# CVE-2022-24770: Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging

> Attackers can inject malicious formulas into CSV files via Gradio's flagging feature, leading to arbitrary code execution when opened in spreadsheet software.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Mar 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-f8xq-q7px-wg8c, PYSEC-2022-229

## What is CVE-2022-24770?

CVE-2022-24770 is a high-severity code injection vulnerability in Gradio Project Gradio, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

`gradio` is an open source framework for building interactive machine learning models and demos. Prior to version 2.8.11, `gradio` suffers from Improper Neutralization of Formula Elements in a CSV File. The `gradio` library has a flagging functionality which saves input/output data into a CSV file on the developer's computer. This can allow a user to save arbitrary text into the CSV file, such as commands. If a program like MS Excel opens such a file, then it automatically runs these commands, which could lead to arbitrary commands running on the user's computer. The problem has been patched as of `2.8.11`, which escapes the saved csv with single quotes. As a workaround, avoid opening csv files generated by `gradio` with Excel or similar spreadsheet programs.

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

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

3 open source packages ship an affected version, including gradio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gradio` | PyPI | All versions | 2.8.11 |
| `gradio` | PyPI | All versions | 2.8.11 |
| `gradio` | PyPI | All versions | 2.8.11 |

Products: Gradio Project Gradio.

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

Upgrade gradio to 2.8.11 or later.

## Is CVE-2022-24770 being exploited?

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

## Other vulnerabilities in Gradio Project Gradio

- [CVE-2024-39236](https://insights.sbomify.com/CVE-2024-39236/): Withdrawn Advisory: Gradio was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py (critical 9.8)
- [CVE-2023-6572](https://insights.sbomify.com/CVE-2023-6572/): Command Injection in gradio-app/gradio (critical 9.6)
- [CVE-2026-49119](https://insights.sbomify.com/CVE-2026-49119/): Gradio < 6.16.0 Path Traversal via FileExplorer.preprocess() (high 8.7)
- [CVE-2025-23042](https://insights.sbomify.com/CVE-2025-23042/): Gradio Blocked Path ACL Bypass Vulnerability (high 8.7)
- [CVE-2024-4325](https://insights.sbomify.com/CVE-2024-4325/): Server-Side Request Forgery (SSRF) in gradio-app/gradio (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24770 is a high-severity code injection vulnerability in Gradio Project Gradio, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-24770 in the wild and no public exploit code.

Affected packages and fixed versions:
- gradio (PyPI): affected all versions; fixed in 2.8.11
- gradio (PyPI): affected all versions; fixed in 2.8.11
- gradio (PyPI): affected all versions; fixed in 2.8.11

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-24770/ (Markdown: https://insights.sbomify.com/CVE-2022-24770/index.md)
```

## Sources

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

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