{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70520 exists.","fix":"No fix has been published for CVE-2025-70520 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-70520 is a critical missing authorization vulnerability in n/a, published on 7 Oct 2026. 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-70520 and fix it if it is affected.\n\nWhat it is: CVE-2025-70520 is a critical missing authorization vulnerability in n/a, published on 7 Oct 2026. 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-70520 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-70520/ (Markdown: https://insights.sbomify.com/CVE-2025-70520/index.md)","id":"CVE-2025-70520","markdown":"https://insights.sbomify.com/CVE-2025-70520/index.md","name":"CVE-2025-70520","record":{"aliases":["GHSA-r46f-86rj-p44j"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fanvil IP phone","requires_auth":"none","summary":"Unauthenticated attackers can access sensitive device resources and logs via the websocket handler due to missing authentication checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"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-306","name":"Missing Authentication for Critical Functionality"}],"description":"The websocket handler of Fanvil x7a firmware version 2.6.0.1182 does not enforce proper authentication restrictions against sessionless users. The lack of restrictions grants anyone the ability to view any device resources such as operational logs or perform diagnostic requests.","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":"Missing authorization in n/a","id":"CVE-2025-70520","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2025-70521"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-70519"},"products":["n/a"],"published":"2026-10-07","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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["n/a"]},"summary":"Unauthenticated attackers can access sensitive device resources and logs via the websocket handler due to missing authentication checks.","url":"https://insights.sbomify.com/CVE-2025-70520/"}