Tikiwiki 1.9.5 contains an information disclosure vulnerability in multiple PHP scripts. When the sort_mode parameter is left empty in requests to various scripts (such as tiki-listpages.php, tiki-lastchanges.php, and others), the application fails to properly handle the input, resulting in database errors that disclose sensitive information, including the MySQL username and password, in the error messages returned to the user.
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 auxiliary module (modules/auxiliary/admin/tikiwiki/tikidblib.rb) targeting an information disclosure vulnerability in TikiWiki version 1.9.5 (CVE-2006-5702). The exploit works by sending a specially crafted HTTP GET request to the /tiki-lastchanges.php endpoint of a vulnerable TikiWiki installation, manipulating the sort_mode parameter to trigger a MySQL error. This error causes the application to disclose sensitive database configuration information, including the MySQL username and password, database name, host, and installation path. The module is operational and provides direct output of the extracted credentials. The only required input is the URI path to the TikiWiki installation (default: /tikiwiki). The code is written in Ruby and is designed to be run 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.