Loading vulnerability…
qcubed, including version 3.1.1 and other versions, contains an SQL injection vulnerability in profile.php. The strQuery POST parameter is incorporated into SQL processing without adequate protection against injected SQL code, allowing an unauthenticated attacker to submit a crafted request and access the database.
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 is an operational exploit tool targeting the QCubed PHP framework, specifically its profile.php endpoint. Written in TypeScript and designed to run with the Bun runtime, the tool automates the process of probing, brute-forcing, and extracting database information from vulnerable QCubed installations. The main entry point is index.ts, which parses command-line arguments to perform various attack modes such as testing for vulnerability, creating attack sessions, brute-forcing table and column names, extracting row data, and attempting data insertion. The tool interacts with the target over HTTP, sending crafted SQL queries to the profile.php endpoint and parsing the responses. Session data and results are stored locally in the ./sites directory. The exploit is not a detection script but provides real exploitation capabilities, allowing attackers to enumerate and extract sensitive database information from vulnerable targets. The README provides clear usage instructions and example commands, indicating a mature and operational exploit.
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.