{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44203 exists.","fix":"No fix has been published for CVE-2025-44203 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-44203 is a high-severity vulnerability in n/a, published on 20 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-44203 and fix it if it is affected.\n\nWhat it is: CVE-2025-44203 is a high-severity vulnerability in n/a, published on 20 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44203 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-44203/ (Markdown: https://insights.sbomify.com/CVE-2025-44203/index.md)","id":"CVE-2025-44203","markdown":"https://insights.sbomify.com/CVE-2025-44203/index.md","name":"CVE-2025-44203","record":{"aliases":["DEBIAN-CVE-2025-44203","GHSA-754w-9jq2-jm5g","UBUNTU-CVE-2025-44203"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"HotelDruid hotel software","requires_auth":"none","summary":"Remote attackers can exploit a race condition in the unauthenticated setup endpoint to disclose admin credentials and cause denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hoteldruid","vendor":"digitaldruid"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"},{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-06-18","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-06-18T18:22:49Z","kind":"github_poc","ref":"https://github.com/IvanT7D3/CVE-2025-44203","stars":0,"title":"CVE-2025-44203 - HotelDruid 3.0.0/3.0.7 - Sensitive Information Disclosure, DoS"}],"tier":"weaponised"},"has_fix":false,"headline":"Race condition in n/a","id":"CVE-2025-44203","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-44206"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2025-44201"},"products":["n/a"],"published":"2025-06-20","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-43371","kev_date_added":null,"published":"2023-09-20"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-43373","kev_date_added":null,"published":"2023-09-20"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-43374","kev_date_added":null,"published":"2023-09-20"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-43375","kev_date_added":null,"published":"2023-09-20"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2021-42949","kev_date_added":null,"published":"2022-09-16"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2021-37832","kev_date_added":null,"published":"2021-08-03"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-9086","kev_date_added":null,"published":"2019-06-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-09","vendors":["n/a"]},"summary":"Remote attackers can exploit a race condition in the unauthenticated setup endpoint to disclose admin credentials and cause denial of service.","url":"https://insights.sbomify.com/CVE-2025-44203/"}