CVE-2025-34116 is a remote command execution vulnerability in IPFire before version 2.19 Core Update 101. The flaw exists in the proxy.cgi CGI interface, specifically via the NCSA user creation form fields. An authenticated attacker can supply crafted input that is incorporated into shell command execution without proper neutralization of special elements, allowing arbitrary shell command injection. Successful exploitation results in command execution in the context of the web server process.
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/ipfire_proxy_exec.rb) that exploits a remote command execution (RCE) vulnerability in IPFire, an open source Linux firewall distribution. The vulnerability exists in the proxy.cgi page for IPFire versions prior to 2.19 Core Update 101 (CVE-2025-34116). The exploit works by sending a specially crafted POST request to /cgi-bin/proxy.cgi, injecting arbitrary commands via the NCSA_PASS parameter. The module requires valid credentials (default: admin) and targets the web interface, typically running on port 444 with SSL enabled. The exploit is operational, allowing customizable command execution on the target system. The repository is structured as a standard Metasploit module, with all logic contained in a single Ruby file.
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.