A static code injection vulnerability exists in inc/function.base.php in Ajax File and Image Manager before version 1.1. This vulnerability, as used in tinymce before 1.4.2, phpMyFAQ 2.6 before 2.6.19, 2.7 before 2.7.1, and possibly other products, allows remote attackers to inject arbitrary PHP code into data.php via crafted parameters. The vulnerable code fails to properly sanitize user-supplied input before writing it to a PHP file, resulting in the execution of attacker-controlled code.
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 (5 hidden).
This repository contains a single Metasploit module targeting a remote code execution vulnerability (CVE-2011-4825) in log1 CMS 2.0. The exploit abuses the 'Ajax File and Image Manager' component, specifically the 'writeInfo()' function in 'function.base.php', which allows arbitrary data to be written to 'data.php' via the 'data' parameter. The module sends a crafted POST request to '/admin/libraries/ajaxfilemanager/ajax_create_folder.php' to inject a PHP payload, then accesses '/admin/libraries/ajaxfilemanager/inc/data.php' to trigger execution. The exploit is fully weaponized, leveraging Metasploit's payload system for customizable PHP code execution. The repository structure is typical for a Metasploit module, with the exploit logic encapsulated 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.
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.