CVE-2010-4335 is a vulnerability in CakePHP versions 1.3.x through 1.3.5 and 1.2.8, specifically in the _validatePost function of libs/controller/components/security.php. The vulnerability arises from the use of the unserialize function on user-supplied data in the data[_Token][fields] parameter, allowing remote attackers to manipulate the internal Cake cache. By crafting a malicious serialized payload, an attacker can modify the file_map cache and potentially execute arbitrary local files, leading to arbitrary code execution.
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/cakephp_cache_corruption.rb) targeting a remote code execution vulnerability in CakePHP (CVE-2010-4335). The exploit abuses a flaw in the Security component's handling of serialized objects, allowing unauthenticated attackers to inject and execute arbitrary PHP code via crafted POST requests. The module is written in Ruby and leverages Metasploit's HttpClient mixin to interact with the target web application. The main configurable endpoint is the POST path (default '/'), and the exploit manipulates the CakePHP cache file '../tmp/cache/persistent/cake_core_file_map' to trigger code execution. The payload is customizable and allows for arbitrary PHP code execution, making this an operational exploit suitable for post-exploitation activities. The repository is structured as a typical Metasploit module, with all logic contained in a single Ruby file.
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.