{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-65823 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-65823 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65823 is a critical vulnerability in n/a, published on 10 Dec 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-65823 and fix it if it is affected.\n\nWhat it is: CVE-2025-65823 is a critical vulnerability in n/a, published on 10 Dec 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-65823 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-65823/ (Markdown: https://insights.sbomify.com/CVE-2025-65823/index.md)","id":"CVE-2025-65823","markdown":"https://insights.sbomify.com/CVE-2025-65823/index.md","name":"CVE-2025-65823","record":{"aliases":["GHSA-27q6-m98q-fwm4"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Meatmeet Pro firmware","requires_auth":"none","summary":"Hardcoded Wi-Fi credentials in Meatmeet Pro firmware allow attackers to access the vendor's network or force device connections to malicious access points.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"meatmeet_pro_wifi_\\\u0026_bluetooth_meat_thermometer_firmware","vendor":"meatmeet"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"The Meatmeet Pro was found to be shipped with hardcoded Wi-Fi credentials in the firmware, for the test network it was developed on. If an attacker retrieved this, and found the physical location of the Wi-Fi network, they could gain unauthorized access to the Wi-Fi network of the vendor. Additionally, if an attacker were located in close physical proximity to the device when it was first set up, they may be able to force the device to auto-connect to an attacker-controlled access point by setting the SSID and password to the same as which was found in the firmware file.","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-65823","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-65824"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2025-65822"},"products":["n/a"],"published":"2025-12-10","related":[{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2025-65824","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2025-65821","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2025-65822","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":6.8,"headline":"Security feature bypass in n/a","id":"CVE-2025-65829","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2025-65828","kev_date_added":null,"published":"2025-12-10"},{"cvss_score":4.6,"headline":"Information disclosure in n/a","id":"CVE-2025-65825","kev_date_added":null,"published":"2025-12-10"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-11","vendors":["n/a"]},"summary":"Hardcoded Wi-Fi credentials in Meatmeet Pro firmware allow attackers to access the vendor's network or force device connections to malicious access points.","url":"https://insights.sbomify.com/CVE-2025-65823/"}