CVE-2025-44203: In HotelDruid 3.0.0 and 3.0.7, the unauthenticated database-setup endpoint creadb.php can be reached before...
In HotelDruid 3.0.0 and 3.0.7, the unauthenticated database-setup endpoint creadb.php can be reached before setup is completed and performs database creation without locking. By sending many concurrent requests, an attacker can trigger a race condition during which verbose SQL error messages disclose the administrator username, password hash, and salt. The same race leaves the setup partially initialized, so the administrator can no longer log in with the credentials set during installation, resulting in a denial of service that requires reinstallation to recover. Remote exploitation additionally requires the installation to allow non-localhost access. The vulnerability was fixed in version 3.0.8.
Security readout for executives and security teams
Plain-English summary
HotelDruid 3.0.0 and 3.0.7 have an installation-time flaw. If the database setup page is reachable remotely before setup finishes, concurrent requests can break setup, expose admin credential-hash details in SQL errors, and leave the administrator unable to log in. The source says this was fixed in 3.0.8.
Executive priority
Prioritize remediation for internet-accessible or recently installed HotelDruid systems. The practical business risk is service outage during installation plus exposure of password-hash material, with recovery potentially requiring reinstallation.
Technical view
The unauthenticated creadb.php setup endpoint performs database creation without locking. A race condition can produce verbose SQL errors disclosing administrator username, password hash, and salt, while also partially initializing setup and causing denial of service. The CVSS vector emphasizes availability impact, but the description also reports credential-hash disclosure.
Likely exposure
Exposure is likely limited to HotelDruid 3.0.0 or 3.0.7 installations where setup is incomplete and non-localhost access to the setup endpoint is allowed. Completed, upgraded, or localhost-only setup environments appear less exposed based on the provided sources.
Exploitation context
The CVE is not listed as KEV, and the bundle does not prove active exploitation. A public GitHub reference exists, so defenders should treat technical details as publicly available without assuming exploitation is occurring in the wild.
Researcher notes
The affected product metadata in the bundle is incomplete, but the description specifically names HotelDruid 3.0.0 and 3.0.7. Fixed version 3.0.8 is stated. Do not infer other versions, default exposure, or active exploitation from the supplied evidence.
Mitigation direction
Upgrade HotelDruid 3.0.0 or 3.0.7 to version 3.0.8 or later.
Restrict setup and installation endpoints to localhost or trusted administrative networks.
Do not expose incomplete HotelDruid installations to the internet.
Reinstall affected partially initialized systems if administrators cannot log in.
Check HotelDruid vendor guidance for any additional recovery instructions.
Validation and detection
Inventory HotelDruid instances and confirm exact deployed versions.
Identify any incomplete installations still reachable over the network.
Verify setup access is limited to localhost or trusted administration paths.
Review installation logs for verbose SQL errors during setup.
Confirm administrators can log in after setup completion.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-209: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.