Loading vulnerability…
In vBulletin 3.0.6 and earlier, the misc.php script, when the "Add Template Name in HTML Comments" feature is enabled, fails to properly sanitize nested variables in the 'template' parameter. This allows remote attackers to inject and execute arbitrary PHP code via crafted input to the template parameter, leading to full compromise of the application.
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 (1 hidden).
This repository contains a single Metasploit module (modules/exploits/unix/webapp/php_vbulletin_template.rb) targeting a remote code execution vulnerability in vBulletin forum software (CVE-2005-0511). The exploit abuses the 'Add Template Name in HTML Comments' feature, which, when enabled, allows arbitrary PHP code execution via the 'template' GET parameter in misc.php. The module sends a specially crafted HTTP GET request to the misc.php endpoint, injecting a user-supplied shell command (encoded as PHP chr() calls) that is executed on the server using passthru(). The exploit is operational and allows the attacker to execute arbitrary commands as the web server user. The only required configuration is the correct path to misc.php (default: /forum/misc.php) and that the vulnerable vBulletin option is enabled. The module 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.
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.