Loading vulnerability…
An unrestricted file upload vulnerability exists in TikiWiki 1.9.4 Sirius and earlier, specifically in the jhot.php script. The vulnerability allows remote attackers to upload arbitrary files with a .php extension via the 'filepath' parameter. Uploaded files are placed in the img/wiki/ directory, enabling attackers to 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 exploit file: modules/exploits/unix/webapp/tikiwiki_jhot_exec.rb. The exploit targets a remote command execution vulnerability in TikiWiki version 1.9.4 (CVE-2006-4602), specifically in the jhot.php script, which fails to properly validate uploaded files. The exploit works by uploading a malicious PHP file (tiki-config.php) to the server via a POST request to /tikiwiki/jhot.php. It then triggers the uploaded file by sending a GET request to /tikiwiki/img/wiki/tiki-config.php with a specially crafted CLIENT-IP HTTP header containing the command to execute. The module supports various command payloads as provided by Metasploit (cmd, bash, etc.). The exploit also includes a check method to verify if the target is running the vulnerable TikiWiki version and a cleanup method to remove the temporary PHP file after exploitation. The structure is typical for a Metasploit module, with clear separation of initialization, vulnerability check, exploitation, and cleanup routines. The main attack vector is network-based, exploiting a web application endpoint. The endpoints involved are fingerprintable and include the upload and trigger URLs for the malicious PHP 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.