Loading vulnerability…
A remote code execution vulnerability exists in X7 Chat versions 2.0.2 through 2.0.5.1, specifically in lib/message.php. The vulnerability arises from the unsafe use of PHP's preg_replace() function with the deprecated /e modifier, which evaluates user-supplied input as PHP code. Authenticated users can exploit this by sending a specially crafted offline message containing malicious PHP code, which is executed when the message is accessed, leading to arbitrary code execution with the privileges of the web server 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.
This repository contains a single Metasploit module (modules/exploits/multi/http/x7chat2_php_exec.rb) that exploits an authenticated remote code execution vulnerability (CVE-2014-8998) in X7 Chat versions 2.0.0 through 2.0.5.1. The exploit targets a flaw in lib/message.php, where user-supplied input is passed to preg_replace() with the /e modifier, allowing arbitrary PHP code execution. The module requires valid credentials and the base path to the X7 Chat installation. It works by sending a crafted message and then triggering code execution via a custom HTTP header. The payload is arbitrary PHP code, base64-encoded, and can be used to gain full control of the target server. The structure is typical for a Metasploit exploit: it includes initialization, a check method, the main exploit logic, and payload delivery. The only relevant endpoints are the main index.php script of the X7 Chat installation and the vulnerable message.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.