An integer overflow exists in PHP 4.4.4 and earlier within the unserialize() function. When a long string is passed to unserialize(), the ZVAL reference counter can overflow, potentially leading to memory corruption and arbitrary code execution. This vulnerability is triggered by remote attackers supplying crafted serialized data to PHP applications that use unserialize() on untrusted input.
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: 'php_unserialize_zval_cookie.rb', which exploits an integer overflow vulnerability (CVE-2007-1286) in the unserialize() function of PHP versions prior to 4.5.0. The exploit targets web applications that unserialize user-supplied data from cookies, such as phpBB2, punBB, WWWThreads, and Deadman Redirect, primarily on Linux x86 systems. The module works by sending a large number of specially crafted HTTP Cookie headers to overflow the ZVAL reference counter, allowing arbitrary code execution. The payload is delivered via the HTTP request and can be customized using Metasploit's payload system. The module includes brute-force logic to target a range of memory addresses, increasing reliability across different Linux distributions. The main attack vector is network-based, exploiting web servers over HTTP. The repository is structured as a typical Metasploit exploit module, written in Ruby, and is operational with customizable payloads.
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.