Loading vulnerability…
A directory traversal vulnerability exists in Fonality trixbox CE 2.6.1 and earlier, specifically in user/index.php, where the langChoice parameter is not properly sanitized. This allows remote attackers to include and execute arbitrary files on the server by supplying crafted input containing directory traversal sequences (..).
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 (2 hidden).
This repository contains a single Metasploit module (trixbox_langchoice.rb) that exploits a Local File Inclusion (LFI) vulnerability in Trixbox CE 2.6.1 (CVE-2008-6825). The exploit works by injecting PHP code into a session file via the 'langChoice' POST parameter to /user/index.php, then triggering the inclusion of that session file to execute the payload. The module is written in Ruby and leverages Metasploit's HttpClient mixin. It allows the attacker to execute arbitrary PHP code on the target server, providing remote code execution capabilities. The exploit targets the Trixbox web application running on Linux, specifically when PHP session files are stored in /tmp. The only file in the repository is the Metasploit module itself, and it is fully operational, supporting customizable PHP payloads.
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.