Loading vulnerability…
CVE-2025-44203 affects HotelDruid 3.0.7. An unauthenticated attacker can send malformed POST requests to the creadb.php endpoint before the 'create database' button is pressed and trigger verbose SQL error messages. These error responses may disclose sensitive database-backed application information, including the administrator username, password hash, and salt. The issue is rooted in improper exposure of detailed SQL error output to unauthenticated users during the database creation workflow. The same attack path may also place the application into a state that causes denial of service by preventing the administrator from logging in even with correct credentials.
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 an exploit for CVE-2025-44203, targeting HotelDruid versions 3.0.0 and 3.0.7. The exploit leverages verbose SQL error messages on the '/hoteldruid/creadb.php' endpoint to disclose sensitive information such as username, password hash, and salt. The main exploit script ('exploit.py') sends a large number of crafted POST requests to the vulnerable endpoint, attempting to trigger the information disclosure. If successful, the attacker can extract the password hash and salt from the error messages. The repository also includes a brute-force script ('brute.py'), which, after manual insertion of the extracted hash and salt, attempts to recover the plaintext password using a supplied wordlist. The README provides detailed usage instructions and context, including configuration requirements for the target and links to the CVE record. The exploit is operational and provides both information disclosure and a potential denial of service (by preventing admin login). The code is written in Python and is straightforward, with clear separation between the exploitation and brute-forcing steps.
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.
2 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.