Loading vulnerability…
A SQL Injection vulnerability exists in the User Stats interface (/vicidial/user_stats.php) of VICIdial, specifically via the file_download parameter. This allows an attacker to inject arbitrary SQL commands into the backend database, leading to a range of possible attacks including identity spoofing, data tampering, full data disclosure, data destruction, and privilege escalation to database administrator.
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 auxiliary scanner module (vicidial_multiple_sqli.rb) targeting multiple authenticated SQL injection vulnerabilities in VICIdial 2.14b0.5 prior to svn/trunk revision 3555. The exploit requires valid user credentials and leverages SQL injection in several parameters across different PHP endpoints (admin.php, AST_agent_time_sheet.php, user_stats.php) to enumerate and extract usernames and password hashes from the vicidial_users table. The module is operational, providing automated extraction of sensitive user data from vulnerable VICIdial instances. The code is written in Ruby and is structured as a standard Metasploit module, making use of the framework's HTTP client and SQLi mixins. No hardcoded IPs or external domains are present; all endpoints are relative to the target VICIdial web application.
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.