# CVE-2024-53924: Pycel allows code injection via a crafted formula

> Attackers can execute arbitrary code by crafting malicious formulas in spreadsheets processed by the Pycel library.

- **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:** 17 Apr 2025
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-pw67-xjhq-389w, PYSEC-2025-177

## What is CVE-2024-53924?

CVE-2024-53924 is a critical code injection vulnerability in n/a, published on 17 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pycel through 1.0b30, when operating on an untrusted spreadsheet, allows code execution via a crafted formula in a cell, such as one beginning with the =IF(A1=200, eval("__import__('os').system( substring.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-53924?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pycel` | PyPI | All versions to 1.0-beta0 | None |
| `pycel` | PyPI | All versions to 1.0b30 | None |
| `pycel` | PyPI | All versions to 1.0b30 | None |

Products: Dgorissen Pycel.

## How do I fix CVE-2024-53924?

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

## Is CVE-2024-53924 being exploited?

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

Public exploit code:

- A PoC of CVE-2024-53924 (github_poc): https://github.com/aelmosalamy/CVE-2024-53924

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53924 and fix it if it is affected.

What it is: CVE-2024-53924 is a critical code injection vulnerability in n/a, published on 17 Apr 2025. 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-2024-53924 exists.

Affected packages and fixed versions:
- pycel (PyPI): affected all versions up to 1.0-beta0; no fix listed
- pycel (PyPI): affected all versions up to 1.0b30; no fix listed
- pycel (PyPI): affected all versions up to 1.0b30; no fix listed

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

## Sources

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

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