CVE-2026-14762 is a SQL injection vulnerability in code-projects Hotel and Tourism Reservation 1.0. The issue affects an unspecified function in /admin/rooms.php within the Room Management Page. According to the provided content, manipulation of the delete argument is not safely handled and can be used to inject attacker-controlled SQL into backend database queries. The vulnerability is remotely exploitable, and public exploit information is available.
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.
Repository is a small Python exploit project with 6 files: two executable scripts (basic_exploit.py and exploit.py), a README, requirements, license, and gitignore. The main functionality is in exploit.py, which implements an operational time-based blind SQL injection exploit for CVE-2026-14762 affecting Code-Projects Hotel & Tourism Reservation 1.0. The vulnerable target is the web endpoint /admin/rooms.php, specifically the GET parameter delete. The exploit constructs conditional SQL payloads using IF(..., SLEEP(delay), 0) to infer truth values from response timing. basic_exploit.py is a minimal detector/PoC that sends a single timing payload to TARGET/admin/rooms.php?delete=... and reports whether the delay suggests vulnerability. exploit.py is the full-featured tool: it parses target URLs, manages a requests session, supports proxies, custom User-Agent, retry logic, SSL verification toggling, and multithreaded multi-target operation via ThreadPoolExecutor. Based on the README and visible code, its capabilities include vulnerability confirmation, current database extraction, table and column enumeration through information_schema, row-by-row data dumping, ad-hoc SQL query extraction, interactive SQL shell behavior over blind inference, file reads using LOAD_FILE(), and file writes using INTO OUTFILE/DUMPFILE. The documented end goal is PHP webshell deployment into a webroot such as /var/www/html, which can lead to remote code execution if the written file is web-accessible. This is not a framework module; it is a standalone Python exploit. It is more than a detector because it includes post-exploitation style database and filesystem actions. Maturity is OPERATIONAL rather than WEAPONIZED because it provides a concrete payload and exploitation workflow, but is not embedded in a larger offensive framework with modular payloading. The repository contains no obvious destructive fake behavior; its logic and documentation are consistent with a real SQLi exploitation utility.
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.
3 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.