Loading vulnerability…
eLabFTW 1.8.5 contains an arbitrary file upload vulnerability in /app/controllers/EntityController.php. An authenticated attacker can send a crafted POST request that uploads a PHP file into the web root. Because the uploaded file is placed in a web-accessible location and interpreted by the server, the flaw can be leveraged to execute attacker-controlled code on the remote system.
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 (1 hidden).
This repository contains a Python exploit script (CVE-2019-12185.py) targeting eLabFTW version 1.8.5, which is vulnerable to arbitrary file upload via the /app/controllers/EntityController.php endpoint. The exploit requires valid user credentials and the base URL of the target. It authenticates to the application, obtains necessary tokens, and uploads a PHP webshell to the /uploads/ directory. The webshell allows remote command execution via HTTP GET requests. The README.md provides detailed usage instructions, example commands, and screenshots demonstrating successful exploitation. The repository is structured with a single exploit script, a README, and a .gitignore. The main attack vector is network-based, exploiting a web application file upload vulnerability to achieve remote code execution.
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.