FusionPBX 4.4.8 contains a command injection vulnerability in the service_edit.php file. An attacker can submit a malicious system command via this file, which is then stored in the database. The malicious command is executed when services.php is accessed with the appropriate service id and the parameter a=start, leading to arbitrary command execution on the server.
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 two exploit implementations for CVE-2019-15029, a remote code execution vulnerability in FusionPBX v4.4.8. The exploit requires valid credentials and leverages the web interface to inject a malicious command into a new service via the 'service_edit.php' endpoint. The command is then triggered by accessing the 'services.php' endpoint with the appropriate parameters. The repository includes: - 'FusionPBX-exploit.py': A standalone Python script that automates the login, payload injection, and execution process, resulting in a reverse shell to the attacker's machine. - 'fusionpbx_services.rb': A Metasploit module that provides a weaponized, customizable exploit for the same vulnerability, supporting Metasploit payloads and automatic cleanup (deleting the malicious service after exploitation). - 'README.md': Documentation describing the exploit and usage instructions, including reference to the Metasploit module. The main attack vector is network-based, targeting the FusionPBX web interface. The endpoints involved are all HTTP(S) paths within the FusionPBX application. The exploit is operational and weaponized, providing remote code execution capabilities to an authenticated attacker.
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.