CVE-2013-6129 is a vulnerability in vBulletin versions 4.1 and 5, specifically in the install/upgrade.php scripts. The flaw allows remote attackers to create administrative accounts by supplying crafted values to the customerid, htmldata[password], htmldata[confirmpassword], and htmldata[email] parameters. This vulnerability was actively exploited in the wild in October 2013.
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 auxiliary module (modules/auxiliary/admin/http/vbulletin_upgrade_admin.rb) that exploits a vulnerability in vBulletin (CVE-2013-6129) affecting versions 4.1+ and 4.5+. The module abuses the 'install/upgrade.php' component to create a new administrator account with attacker-supplied credentials. The exploit works by sending a specially crafted POST request to the '/install/upgrade.php' endpoint with parameters that trigger the creation of a new admin user. The module requires the attacker to specify the target URI, username, password, and email for the new account. If successful, the module reports the creation of the new admin account and stores the credentials. The code is written in Ruby and is designed to be run within the Metasploit framework. The repository is operational and provides a working exploit for the targeted vulnerability.
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.