Loading vulnerability…
CVE-2024-53924 affects Pycel through version 1.0b30. When Pycel processes an untrusted spreadsheet, a crafted cell formula can trigger code execution. The provided example indicates that attacker-controlled formula content can reach Python evaluation logic, e.g. via a formula beginning with =IF(A1=200, eval("__import__('os').system(, resulting in execution of arbitrary Python code and potentially OS commands. In practical terms, the vulnerability is a code injection issue in Pycel's handling/evaluation of spreadsheet formulas from untrusted input.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository demonstrates a proof-of-concept (PoC) exploit for CVE-2024-53924, a code execution vulnerability in the Pycel Python library (up to version 1.0b30). The repository contains two files: a detailed README.md describing the vulnerability, exploitation steps, and impact, and a Python script (poc.py) that loads and evaluates an Excel file using Pycel. The exploit works by crafting a malicious Excel formula (e.g., using eval and __import__('os').system) that, when evaluated by Pycel, results in arbitrary code execution. The PoC script loads a user-supplied or default Excel file, evaluates a cell, and demonstrates how setting a cell value can trigger the malicious formula. The attack vector is local, requiring the victim to process a malicious Excel file with Pycel. The main fingerprintable endpoint is the Excel file (example.xlsx) used as the attack vector. The exploit is a PoC and does not include a weaponized or automated payload, but clearly demonstrates the risk of using Pycel with untrusted input.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.