Loading vulnerability…
CVE-2012-5692 refers to an unspecified vulnerability in the admin/sources/base/core.php file of Invision Power Board (IPB) versions 3.1.x through 3.3.x. The details of the vulnerability, including the nature of the flaw, the vulnerable function, and the method of exploitation, have not been disclosed.
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 (2 hidden).
This repository contains a single Metasploit module targeting a PHP unserialize() vulnerability (CVE-2012-5692) in Invision IP.Board <= 3.3.4. The exploit abuses a flaw in '/admin/sources/base/core.php', which unserializes user-controlled data from cookies, allowing unauthenticated remote code execution. The module works by crafting a malicious serialized object in a cookie, which, when processed by the vulnerable code, writes a PHP payload to the 'cache/' directory on the server. The payload is then executed via an HTTP request, providing the attacker with a remote shell (including Meterpreter support). The module is operational and requires only network access to the target web application. The code is written in Ruby and is structured as a standard Metasploit exploit module, with clear separation of initialization, vulnerability checking, exploitation, and cleanup routines.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.