← Back
CVE-2024-53924
Code Injection in pycel (CVE-2024-53924)
Summary
code injection in pycel (CVE-2024-53924). Successful exploitation can lead to full system takeover.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-53924** has been found in pycel.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "pycel CVE-2024-53924" on the vendor's site.
CVE-2024-53924 (pycel) — CWE-94 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**arbitrary code execution** (CWE-94) exists in pycel.
📍 Affected scope
pycel — .
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'pycel' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pycel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pycel` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
pycel
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.0-beta0"},{"last_affected":"1.0-beta11"},{"last_affected":"1.0-beta12"},{"last_affected":"1.0-beta13"},{"last_affected":"1.0-beta14"},{"last_affected":"1.0-beta15"},{"last_affected":"1.0-beta16"},{"last_affected":"1.0-beta17"},{"last_affected":"1.0-beta18"},{"last_affected":"1.0-beta19"},{"last_affected":"1.0-beta2"},{"last_affected":"1.0-beta20"},{"last_affected":"1.0-beta21"},{"last_affected":"1.0-beta22"},{"last_affected":"1.0-beta26"},{"last_affected":"1.0-beta27"},{"last_affected":"1.0-beta28"},{"last_affected":"1.0-beta29"},{"last_affected":"1.0-beta3"},{"last_affected":"1.0-beta30"},{"last_affected":"1.0-beta4"},{"last_affected":"1.0-beta5"},{"last_affected":"1.0-beta6"},{"last_affected":"1.0-beta7"},{"last_affected":"1.0-beta8"}]}]
pip
pycel
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-53924
- advisory https://github.com/advisories/GHSA-pw67-xjhq-389w
- package https://github.com/dgorissen/pycel
- package https://github.com/stephenrauch/pycel
- package https://pypi.org/project/pycel/
- report https://gist.github.com/aelmosalamy/cb098e61939718d2bb248fd1cc94f287
- web https://pypi.org/project/pycel
- web https://github.com/pypa/advisory-database/tree/main/vulns/pycel/PYSEC-2025-177.yaml