Loading vulnerability…
CVE-2026-41462 is an unauthenticated SQL injection vulnerability affecting ProjeQtor versions 7.0 through 12.4.3. The flaw is in the login functionality, where the user-supplied login value is directly concatenated into a SQL query without parameterization or sanitization. An attacker can submit crafted input in the username field to the authentication endpoint and inject arbitrary SQL expressions. Based on the provided information, successful exploitation can be used to manipulate authentication-related data, create privileged accounts, extract sensitive information from the backend database, and potentially reach operating system command execution when the underlying database account has sufficiently elevated privileges.
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.
Small repository containing a standalone Python exploit, a YAML detection template, and documentation. The main capability is unauthenticated SQL injection against ProjeQtor login functionality (claimed affected versions 7.0 through 12.4.3) to create a new administrative account by injecting an INSERT statement into the login parameter. The Python script uses requests.Session, accepts a target URL and optional proxy, builds the target login endpoint with urljoin, and POSTs crafted form data to /login.php. Although it exposes a --create-admin flag, the current code always prepares and sends the admin-creation payload regardless of that flag. It reports success based primarily on receiving HTTP 200, so validation is minimal. The YAML file is a detection template rather than an exploit: it sends a benign SQLi probe to /login.php, /projeqtor/login.php, or /login and matches SQL error strings and status codes 200/500. Overall, the repository purpose is dual-use: practical exploitation via account creation plus vulnerability detection/fingerprinting via the YAML template.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.