{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-46660 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-46660 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46660 is a medium-severity vulnerability in n/a, published on 6 Aug 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-46660 and fix it if it is affected.\n\nWhat it is: CVE-2025-46660 is a medium-severity vulnerability in n/a, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-46660 in the wild and no public exploit code.\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-46660/ (Markdown: https://insights.sbomify.com/CVE-2025-46660/index.md)","id":"CVE-2025-46660","markdown":"https://insights.sbomify.com/CVE-2025-46660/index.md","name":"CVE-2025-46660","record":{"aliases":["GHSA-gvxw-cj6r-74wg"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Exonaut server software","requires_auth":"none","summary":"Attackers can crack stored passwords more easily because Exonaut hashes them without salt, exposing user credentials.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"exonaut","vendor":"4cstrategies"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"description":"An issue was discovered in 4C Strategies Exonaut 21.6. Passwords, stored in the database, are hashed without a salt.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Weak cryptography in n/a","id":"CVE-2025-46660","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in Metazo","id":"CVE-2025-46661"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-46659"},"products":["n/a"],"published":"2025-08-06","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2025-46658","kev_date_added":null,"published":"2025-08-05"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2025-46659","kev_date_added":null,"published":"2025-08-06"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2024-55401","kev_date_added":null,"published":"2025-08-07"},{"cvss_score":6.5,"headline":"4C Strategies Exonaut before v22.4 was discovered to contain insecure permissions.","id":"CVE-2024-55398","kev_date_added":null,"published":"2025-08-06"},{"cvss_score":6.5,"headline":"Server-side request forgery in n/a","id":"CVE-2024-55399","kev_date_added":null,"published":"2025-08-06"},{"cvss_score":5.3,"headline":"4C Strategies Exonaut before v22.4 was discovered to contain an access control issue.","id":"CVE-2024-55402","kev_date_added":null,"published":"2025-08-06"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-06","vendors":["n/a"]},"summary":"Attackers can crack stored passwords more easily because Exonaut hashes them without salt, exposing user credentials.","url":"https://insights.sbomify.com/CVE-2025-46660/"}