{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26075 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26075 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26075 is a medium-severity SQL injection vulnerability in Cisco IoT Field Network Director (IoT-FND), published on 18 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-26075 and fix it if it is affected.\n\nWhat it is: CVE-2020-26075 is a medium-severity SQL injection vulnerability in Cisco IoT Field Network Director (IoT-FND), published on 18 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-26075 in the wild and no public exploit code.\n\nAffected product: Cisco IoT Field Network Director (IoT-FND). 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-2020-26075/ (Markdown: https://insights.sbomify.com/CVE-2020-26075/index.md)","id":"CVE-2020-26075","markdown":"https://insights.sbomify.com/CVE-2020-26075/index.md","name":"CVE-2020-26075","record":{"aliases":["GHSA-7fm5-2jq2-jjhm"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Cisco IoT Field Network Director","requires_auth":"low_privilege","summary":"An authenticated attacker can exploit insufficient input validation in the REST API to access the back-end database of Cisco IoT Field Network Director devices.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"iot_field_network_director","vendor":"cisco"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A vulnerability in the REST API of Cisco IoT Field Network Director (FND) could allow an authenticated, remote attacker to gain access to the back-end database of an affected device. The vulnerability is due to insufficient input validation of REST API requests that are made to an affected device. An attacker could exploit this vulnerability by crafting malicious API requests to the affected device. A successful exploit could allow the attacker to gain access to the back-end database of the affected device.","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":"Cisco IoT Field Network REST API Insufficient Input Validation Vulnerability","id":"CVE-2020-26075","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cisco IoT Field Network Director Information Disclosure Vulnerability","id":"CVE-2020-26076"},"packages":[],"prev":{"headline":"Cisco SD-WAN vManage Privilege Escalation Vulnerability","id":"CVE-2020-26074"},"products":["Cisco IoT Field Network Director (IoT-FND)"],"published":"2020-11-18","related":[{"cvss_score":9.8,"headline":"Cisco IoT Field Network Director Unauthenticated REST API Vulnerability","id":"CVE-2020-3531","kev_date_added":null,"published":"2020-11-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in Cisco IoT Field Network Director","id":"CVE-2018-0270","kev_date_added":null,"published":"2018-05-17"},{"cvss_score":8.7,"headline":"Cisco IoT Field Network Director SOAP API Authorization Bypass Vulnerability","id":"CVE-2020-26072","kev_date_added":null,"published":"2020-11-18"},{"cvss_score":7.7,"headline":"Cisco IoT Field Network Director Remote Device Denial of Service Vulnerability","id":"CVE-2026-20167","kev_date_added":null,"published":"2026-05-06"},{"cvss_score":7.5,"headline":"Cisco IoT Field Network Director Missing API Authentication Vulnerability","id":"CVE-2020-3392","kev_date_added":null,"published":"2020-11-18"},{"cvss_score":7.5,"headline":"Cisco IoT Field Network Director Denial of Service Vulnerability","id":"CVE-2020-3162","kev_date_added":null,"published":"2020-04-15"},{"cvss_score":7.5,"headline":"Cisco IoT Field Network Director Resource Exhaustion Denial of Service Vulnerability","id":"CVE-2019-1644","kev_date_added":null,"published":"2019-01-23"}],"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":"2024-11-13","vendors":["Cisco"]},"summary":"An authenticated attacker can exploit insufficient input validation in the REST API to access the back-end database of Cisco IoT Field Network Director devices.","url":"https://insights.sbomify.com/CVE-2020-26075/"}