Loading vulnerability…
CVE-2011-10011 affects WeBid 1.0.2. The vulnerability is in the converter.php script, which fails to sanitize attacker-controlled input supplied in the to parameter of a POST request. That input is written directly into includes/currencies.php, allowing an unauthenticated attacker to inject arbitrary PHP code into a server-side application file. Because the injected code is stored in a PHP file that is later accessed or included by the application, exploitation results in persistent remote code execution.
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/webid_converter.rb) targeting a remote code execution vulnerability in WeBid version 1.0.2 (CVE-2011-10011). The exploit abuses the converter.php endpoint to inject arbitrary PHP code into includes/currencies.php without authentication. The module first checks for the presence and version of WeBid by accessing /WeBid/docs/changes.txt and /WeBid/converter.php. The main exploit sends a crafted POST request to /WeBid/converter.php, injecting the payload, and then triggers code execution by accessing /WeBid/includes/currencies.php. If a Meterpreter payload is used, the module can also attempt to clean up by restoring the original currencies.php file. The exploit is operational, allowing for arbitrary PHP code execution on the target server. The only file in the repository is a Ruby script compatible with 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.