Loading vulnerability…
CVE-2022-44384 is an arbitrary file upload vulnerability affecting rConfig v3.9.6. According to the provided content, the application allows an attacker to upload a crafted PHP file, which can then be executed by the server. This indicates insufficient validation or restriction of uploaded file types, enabling an attacker to place executable server-side code on the target system and trigger its execution.
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 targeting rConfig (<= 3.9.6) for authenticated remote code execution via an arbitrary file upload vulnerability (CVE-2022-44384). The exploit requires valid admin credentials for the rConfig web interface. It works by authenticating to the application, uploading a PHP payload to the vulnerable endpoint (/lib/crud/vendors.crud.php), and then triggering the payload by accessing it via /images/vendor/<payload_file>.php. The module leverages Metasploit's CmdStager to deliver a customizable PHP payload, typically resulting in a reverse shell. The code is well-structured, weaponized, and ready for operational use within the Metasploit framework. The only file present is the exploit module itself, written in Ruby, and it makes use of several Metasploit mixins for HTTP communication, file dropping, and command staging.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.