Loading vulnerability…
CVE-2011-10018 affects myBB version 1.6.4, which was distributed with an unauthorized backdoor embedded in the source code during packaging rather than as part of the intended application logic. The backdoor could be triggered by supplying a specially crafted collapsed cookie containing attacker-controlled payload data, which the malicious code would process in a way that enabled execution of arbitrary PHP code on the server. The issue is therefore not a conventional implementation bug in a legitimate feature, but a maliciously introduced backdoor in the distributed software package.
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/unix/webapp/mybb_backdoor.rb) that exploits a backdoor in myBB version 1.6.4. The exploit leverages a vulnerability where arbitrary PHP code can be executed on the server by sending a specially crafted HTTP request with a malicious cookie. The module is weaponized, supporting customizable PHP payloads via Metasploit's payload system. The main attack vector is network-based, targeting the web application over HTTP. The only fingerprintable endpoint is the configurable URI path to the myBB installation (default: /index.php). The module includes a check method to verify if the target is accessible and a full exploit method to deliver the payload. The exploit targets myBB 1.6.4 (PHP platform) and is associated with CVE-2011-10018.
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.
3 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.