Kohana versions through 3.3.6 are vulnerable to SQL Injection due to improper sanitization of user-supplied input in the order_by() parameter. If an attacker can control the value passed to order_by(), they can inject arbitrary SQL into queries constructed by the framework, potentially leading to unauthorized data access or manipulation.
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 provides a complete Dockerized environment to demonstrate and exploit CVE-2019-8979, a SQL injection vulnerability in koseven versions prior to 3.3.10. The structure includes Dockerfiles and configuration for both the vulnerable PHP application (based on koseven 3.3.9) and a MySQL database, as well as an exploit container. The vulnerable endpoint is /member, which is susceptible to SQL injection via the 'order' parameter due to improper input sanitization in the Controller_Member::action_index method. The exploit is implemented in Python (exploit/exploit.py) and leverages the albatar library to perform blind, boolean-based SQL injection, extracting information such as the current database, user, and available users and databases. The run.sh script automates the setup and execution of the exploit. The repository is a proof-of-concept and is intended for demonstration and testing purposes.
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.