Loading vulnerability…
GLPI versions prior to 9.4.6 contain a command injection vulnerability in the backup functionality. An attacker with Maintenance privileges and the ability to add WIFI networks can abuse the backup feature to execute arbitrary system commands. While theoretically possible via CSRF without authentication, practical exploitation requires a privileged account.
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 (2 hidden).
This repository contains a Python 3 exploit for CVE-2020-11060, a remote code execution vulnerability in GLPI versions 0.85-9.4.5. The main file, CVE-2020-11060.py, automates the exploitation process: it authenticates to the target GLPI instance using provided credentials, abuses the vulnerability to upload a randomly named PHP webshell to a writable directory (default: 'sound'), and then allows the attacker to execute arbitrary commands via HTTP requests to the webshell. The script supports both Windows and Unix targets and can be used to directly execute commands or to establish persistent access via the webshell. The README.md provides detailed usage instructions and example output, including the URLs of uploaded shells and the expected responses. The exploit requires network access to the target and valid GLPI credentials. The payload is a PHP webshell, and the attack vector is network-based HTTP requests to the GLPI application.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.