CVE-2020-13851 is a remote command execution vulnerability affecting Artica Pandora FMS 7.44. According to the provided information, the flaw is exposed through the product's events feature, which allows an attacker to achieve command execution remotely. Specific vulnerable functions, parameters, or code paths are not provided in the available content.
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 contains a single Metasploit module (modules/exploits/linux/http/pandora_fms_events_exec.rb) that exploits a remote command execution vulnerability (CVE-2020-13851) in Pandora FMS versions 7.0 NG 742, 743, and 744. The exploit targets the 'Events' feature of Pandora FMS, abusing the 'target' parameter in HTTP POST requests to inject and execute arbitrary commands on the server. The module requires valid Pandora FMS credentials (non-admin is sufficient) and interacts with the web interface at /pandora_console/. Upon successful exploitation, it can deliver a reverse shell (Meterpreter or bash) or execute arbitrary commands, and attempts to extract the MySQL database password from the Pandora FMS configuration file. The code is written in Ruby and leverages Metasploit's HttpClient and CmdStager mixins, making it a weaponized, customizable exploit suitable for post-authentication remote code execution on vulnerable Pandora FMS 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.
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.