Loading vulnerability…
Pi-hole Core version 5.2.4 contains multiple privilege-escalation vulnerabilities. The available information does not identify the affected functions, attack vectors, or technical flaw classes.
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 exploit file: modules/exploits/linux/local/pihole_remove_commands_lpe.rb. The module targets a local privilege escalation vulnerability (CVE-2021-29449) in Pi-Hole versions 3.0 through 5.3. The vulnerability arises from improper input validation in the removecustomcname, removecustomdns, and removestaticdhcp commands, which are accessible to the 'www-data' user via sudo without a password. The exploit works by injecting arbitrary commands into these Pi-Hole commands, allowing escalation to root. The module supports three attack methods (DHCP, DNS, CNAME), each manipulating a different Pi-Hole configuration file. The default payload is a reverse PHP shell over SSL, but any Metasploit payload compatible with command execution can be used. The exploit is operational and requires the attacker to have a shell as 'www-data' on a vulnerable Pi-Hole installation. The code is well-structured, leverages Metasploit's local exploit and post-exploitation libraries, and provides clear checks for vulnerability and exploitation steps. No network endpoints are hardcoded; all exploitation is performed locally via file and command manipulation.
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.