{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25749 exists.","fix":"No fix has been published for CVE-2025-25749 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25749 is a high-severity vulnerability in n/a, published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-25749 and fix it if it is affected.\n\nWhat it is: CVE-2025-25749 is a high-severity vulnerability in n/a, published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25749 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-25749/ (Markdown: https://insights.sbomify.com/CVE-2025-25749/index.md)","id":"CVE-2025-25749","markdown":"https://insights.sbomify.com/CVE-2025-25749/index.md","name":"CVE-2025-25749","record":{"aliases":["DEBIAN-CVE-2025-25749","GHSA-2q6p-3x6p-8mcf","UBUNTU-CVE-2025-25749"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"HotelDruid property management","requires_auth":"low_privilege","summary":"HotelDruid allows weak passwords due to missing strength enforcement, potentially enabling account takeover by attackers.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hoteldruid","vendor":"digitaldruid"}],"cvss":{"score":7.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-521","name":"Weak Password Requirements"}],"description":"An issue in HotelDruid version 3.0.7 and earlier allows users to set weak passwords due to the lack of enforcement of password strength policies.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-03-07","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-03-07T12:18:47Z","kind":"github_poc","ref":"https://github.com/huyvo2910/CVE-2025-25749-Weak-Password-Policy-in-HotelDruid-3.0.7","stars":0,"title":null}],"tier":"weaponised"},"has_fix":false,"headline":"Weak cryptography in n/a","id":"CVE-2025-25749","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2025-25758"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-25748"},"products":["n/a"],"published":"2025-03-11","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-24","vendors":["n/a"]},"summary":"HotelDruid allows weak passwords due to missing strength enforcement, potentially enabling account takeover by attackers.","url":"https://insights.sbomify.com/CVE-2025-25749/"}