Loading vulnerability…
CVE-2024-8465 is an SQL injection vulnerability in /jobportal/admin/user/controller.php, where the user_id parameter is not properly sanitized, allowing an attacker to inject arbitrary SQL queries. This can be exploited by sending a specially crafted user_id value, enabling unauthorized access to the backend database and retrieval of all stored information.
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 (1 hidden).
Repository purpose: an intentionally vulnerable PHP/MySQL web application used as a proof-of-concept to demonstrate SQL injection issues inspired by CVE-2024-8465 (academic/educational). Key exploit capabilities (implemented as vulnerabilities rather than an automated exploit tool): - Authentication bypass via SQL injection in app/login.php: user-controlled POST parameters are concatenated into a SELECT against the users table. README provides example payload: ' OR '1'='1' -- (notably effective when targeting the admin path where username is fixed to 'admin' and password is injected). - Unauthorized data disclosure via SQL injection in app/search.php: user-controlled GET parameter q is concatenated into a LIKE clause, enabling dumping all rows from employees (example payload: %' OR '1'='1' --). - Additional SQL injection in app/admin/user/controller.php: GET user_id is used directly in "WHERE id = $user_id" without quoting or validation, enabling boolean-based injection (e.g., 1 OR 1=1) to enumerate user records. Repository structure: - app/: PHP web application - config.php: starts session and connects to MySQL using host 'db' and credentials root/root to database app_db. - index.php: login form / post-login landing. - login.php: vulnerable authentication logic (string concatenation into SQL). - search.php: vulnerable employee search (string concatenation into SQL). - admin/user/controller.php: vulnerable user lookup by id. - logout.php, error.php, styles.css: supporting files. - database/init.sql: creates app_db with users and employees tables and seeds sample data (admin/admin123, user1/user123; employees with salary field). - Dockerfile + docker-compose.yml: runnable lab environment (web on localhost:8080; MySQL 5.7 container initialized with init.sql). - exploit/sqli_payloads.txt and docs/exploit-explanation.md are present but empty; the README contains the actual example payloads and usage guidance. Overall: This is a runnable vulnerable lab/PoC rather than a standalone exploit script. The primary “exploit” interaction is sending crafted HTTP parameters to the exposed PHP endpoints to trigger SQLi for auth bypass and data extraction.
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.
1 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.