{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51055 exists.","fix":"No fix has been published for CVE-2025-51055 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-51055 is a high-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-51055 and fix it if it is affected.\n\nWhat it is: CVE-2025-51055 is a high-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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51055 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-51055/ (Markdown: https://insights.sbomify.com/CVE-2025-51055/index.md)","id":"CVE-2025-51055","markdown":"https://insights.sbomify.com/CVE-2025-51055/index.md","name":"CVE-2025-51055","record":{"aliases":["GHSA-mpm3-wr5w-85gh"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Vedo Suite","requires_auth":"none","summary":"Attackers can read clear-text credentials and secret keys from a configuration file, leading to data exposure and potential account takeover.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vedo_suite","vendor":"vedo_suite_project"}],"cvss":{"score":8.6,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"Insecure Data Storage of credentials has been found in /api_vedo/configuration/config.yml file in Vedo Suite version 2024.17. This file contains clear-text credentials, secret keys, and database information.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-51055","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2025-51056"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2025-51054"},"products":["n/a"],"published":"2025-08-06","related":[{"cvss_score":8.2,"headline":"File upload in n/a","id":"CVE-2025-51056","kev_date_added":null,"published":"2025-08-06"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2025-51052","kev_date_added":null,"published":"2025-08-06"},{"cvss_score":6.5,"headline":"Auth bypass in n/a","id":"CVE-2025-51054","kev_date_added":null,"published":"2025-08-06"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2025-51057","kev_date_added":null,"published":"2025-08-06"},{"cvss_score":6.5,"headline":"Server-side request forgery in n/a","id":"CVE-2025-51058","kev_date_added":null,"published":"2025-08-06"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-51053","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can read clear-text credentials and secret keys from a configuration file, leading to data exposure and potential account takeover.","url":"https://insights.sbomify.com/CVE-2025-51055/"}