{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-25727 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-25727 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25727 is a medium-severity vulnerability in n/a, published on 27 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-25727 and fix it if it is affected.\n\nWhat it is: CVE-2025-25727 is a medium-severity vulnerability in n/a, published on 27 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-25727 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-25727/ (Markdown: https://insights.sbomify.com/CVE-2025-25727/index.md)","id":"CVE-2025-25727","markdown":"https://insights.sbomify.com/CVE-2025-25727/index.md","name":"CVE-2025-25727","record":{"aliases":["GHSA-rwpx-f8qj-4h9h"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bosscomm IF740","requires_auth":"none","summary":"Attackers can read cleartext passwords from Bosscomm IF740 devices, potentially leading to unauthorized access and data exposure.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.2,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-256","name":"Plaintext Storage of a Password"}],"description":"Bosscomm IF740 Firmware versions:11001.7078 \u0026 v11001.0000 and System versions: 6.25 \u0026 6.00 were discovered to store passwords in cleartext.","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":"Hardcoded credentials in n/a","id":"CVE-2025-25727","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":"Information disclosure in n/a","id":"CVE-2025-25728"},"packages":[],"prev":{"headline":"Denial of service in libarchive","id":"CVE-2025-25724"},"products":["n/a"],"published":"2025-02-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-03-19","vendors":["n/a"]},"summary":"Attackers can read cleartext passwords from Bosscomm IF740 devices, potentially leading to unauthorized access and data exposure.","url":"https://insights.sbomify.com/CVE-2025-25727/"}