Pandora FMS 3.1 and earlier are vulnerable due to a default configuration that sets the loginhash_pwd field to an empty string. This allows remote attackers to bypass authentication by sending a specially crafted request to index.php, using 'admin' as the loginhash_user and the MD5 hash of 'admin' as the loginhash_data parameter.
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 single Metasploit module (pandora_upload_exec.rb) that exploits an authentication bypass and arbitrary file upload vulnerability in Pandora FMS v3.1 (CVE-2010-4279). The exploit works by sending a crafted GET request to the login page with specific parameters to bypass authentication, then uploading a PHP payload to the '/images/' directory using the application's built-in file upload functionality. After uploading, the module triggers the payload by sending a GET request to the uploaded PHP file, resulting in remote code execution. The module is written in Ruby and leverages Metasploit's HttpClient and FileDropper mixins. The only file in the repository is the exploit module itself, and it is fully operational, allowing attackers to gain remote access to vulnerable Pandora FMS v3.1 installations.
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.