Loading vulnerability…
A command injection vulnerability exists in rConfig before version 3.9.5. The vulnerability is due to the nodeId parameter in lib/crud/search.crud.php being passed directly to the exec function without proper escaping or sanitization. This allows an attacker to inject arbitrary system commands via a crafted GET request.
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 Python exploit script (rConfig_rce.py) and a README.md. The exploit targets rConfig version 3.9.4, combining SQL injection and command injection vulnerabilities. The script automates the process of extracting the database name and user credentials (including password hashes) via SQL injection, attempts to crack the admin password hash using hashcat and the rockyou wordlist, and, if successful, uses the credentials to perform command injection via a vulnerable search endpoint to spawn a reverse shell to the attacker's machine. The script requires Python 3, the requests library, hashcat, and appropriate wordlists/rules. The README provides detailed usage instructions and context. The main attack vectors are network-based, exploiting web endpoints on the target rConfig instance. The exploit is operational, providing a working end-to-end attack chain from information disclosure to remote code execution.
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.