Loading vulnerability…
CVE-2024-43363 is a remote code execution vulnerability in Cacti prior to version 1.2.28. An authenticated admin can create a device with a hostname containing PHP code, and by repeating the installation process (specifically completing only step 5), configure Cacti to use a PHP file as the log file. When the malicious hostname is logged (log poisoning), accessing the log file URL triggers execution of the injected PHP code, resulting in RCE.
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 Python proof-of-concept exploit for CVE-2024-43363, a remote code execution vulnerability in Cacti (version 1.2.27). The exploit leverages log poisoning by injecting PHP code into a device name, which is then written to the logs. If the logs are accessed in a way that executes the PHP code, arbitrary commands can be run on the server. The repository consists of a README.md explaining the vulnerability and usage, and a single exploit script (cacti_exploit.py). The script performs three main actions: (1) checks if the target Cacti instance is running a vulnerable version, (2) creates a device with a PHP payload in its name, and (3) checks the logs for the injected code. The exploit requires the attacker to have a valid token to create a device. The main attack vector is network-based, targeting HTTP endpoints on the Cacti server. The payload used is a simple PHP command execution snippet.
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.