CVE-2025-34103 is an unauthenticated command injection vulnerability affecting WePresent WiPG-1000 firmware versions prior to 2.2.3.0. The flaw is in the undocumented /cgi-bin/rdfs.cgi endpoint, where the Client parameter is improperly handled and not sanitized before being passed to a system call. As a result, a remote attacker can supply crafted input to inject and execute arbitrary operating system commands 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/wipg1000_cmd_injection.rb) that exploits a command injection vulnerability (CVE-2025-34103) in the WePresent WiPG-1000 wireless presentation device (firmware <=2.0.0.7). The exploit targets the undocumented CGI endpoint '/cgi-bin/rdfs.cgi' and injects arbitrary shell commands via the 'Client' POST parameter. The module includes a check method to verify vulnerability by looking for a specific string in the HTTP response. The payload is a shell command, and the exploit is operational, allowing remote code execution on vulnerable devices. The code is written in Ruby and is designed to be used within the Metasploit framework.
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.