The tiki-graph_formula.php script in TikiWiki 1.9.8 is vulnerable to remote code execution due to improper handling of user-supplied input in the 'f' array parameter. The input is passed directly to PHP's create_function, allowing attackers to inject and execute arbitrary PHP code on the server.
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/tikiwiki_graph_formula_exec.rb) targeting a remote code execution vulnerability in TikiWiki (<= 1.9.8), specifically in the tiki-graph_formula.php script. The exploit leverages improper input sanitization in the 'f' parameter, allowing attackers to execute arbitrary PHP code via crafted HTTP requests. The module first checks if the target is running a vulnerable version of TikiWiki by querying tiki-index.php. Upon exploitation, it attempts to read the db/local.php file to extract database credentials and then executes a user-supplied PHP payload, which can be used for further compromise (e.g., reverse shell, Meterpreter). The exploit is operational, providing real code execution and credential extraction capabilities. The main attack vector is network-based, exploiting a web application endpoint. The repository is structured as a standard Metasploit module, written in Ruby, and is intended for use within the Metasploit Framework.
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.