{"answers":{"affected":"It affects 14 products.","exploited":"There is no known exploitation of CVE-2020-26912 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26912 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26912 is a high-severity vulnerability in Netgear D6200 Firmware, published on 9 Oct 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-26912 and fix it if it is affected.\n\nWhat it is: CVE-2020-26912 is a high-severity vulnerability in Netgear D6200 Firmware, published on 9 Oct 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-26912 in the wild and no public exploit code.\n\nAffected product: Netgear D6200 Firmware. 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-26912/ (Markdown: https://insights.sbomify.com/CVE-2020-26912/index.md)","id":"CVE-2020-26912","markdown":"https://insights.sbomify.com/CVE-2020-26912/index.md","name":"CVE-2020-26912","record":{"aliases":["GHSA-3hjj-hrqp-h46r"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NETGEAR router","requires_auth":"none","summary":"Attackers can perform unauthorized actions on NETGEAR routers via CSRF, requiring firmware upgrades to mitigate.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"d6200_firmware","vendor":"netgear"},{"product":"d7000_firmware","vendor":"netgear"},{"product":"jr6150_firmware","vendor":"netgear"},{"product":"r6020_firmware","vendor":"netgear"},{"product":"r6050_firmware","vendor":"netgear"},{"product":"r6080_firmware","vendor":"netgear"},{"product":"r6120_firmware","vendor":"netgear"},{"product":"r6220_firmware","vendor":"netgear"},{"product":"r6260_firmware","vendor":"netgear"},{"product":"r6700v2_firmware","vendor":"netgear"},{"product":"r6800_firmware","vendor":"netgear"},{"product":"r6900v2_firmware","vendor":"netgear"},{"product":"r7450_firmware","vendor":"netgear"},{"product":"wnr2020_firmware","vendor":"netgear"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:H/AV:A/A:N/C:H/I:H/PR:N/S:C/UI:R","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Certain NETGEAR devices are affected by CSRF. This affects D6200 before 1.1.00.38, D7000 before 1.0.1.78, JR6150 before 1.0.1.24, R6020 before 1.0.0.42, R6050 before 1.0.1.24, R6080 before 1.0.0.42, R6120 before 1.0.0.66, R6220 before 1.1.0.100, R6260 before 1.1.0.64, R6700v2 before 1.2.0.62, R6800 before 1.2.0.62, R6900v2 before 1.2.0.62, R7450 before 1.2.0.62, and WNR2020 before 1.1.0.62.","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":"Cross-site request forgery in n/a","id":"CVE-2020-26912","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"netgear:d6200_firmware","products":["netgear:d6200_firmware","netgear:d7000_firmware","netgear:jr6150_firmware","netgear:r6020_firmware","netgear:r6050_firmware","netgear:r6080_firmware","netgear:r6120_firmware","netgear:r6220_firmware","netgear:r6260_firmware","netgear:r6800_firmware","netgear:wnr2020_firmware"],"type":"csrf","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2020-26913"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-26911"},"products":["n/a"],"published":"2020-10-09","related":[{"cvss_score":9.4,"headline":"Auth bypass in n/a","id":"CVE-2020-26908","kev_date_added":null,"published":"2020-10-09"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-18716","kev_date_added":null,"published":"2020-04-24"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-18717","kev_date_added":null,"published":"2020-04-24"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-18718","kev_date_added":null,"published":"2020-04-24"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-18719","kev_date_added":null,"published":"2020-04-24"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2017-18720","kev_date_added":null,"published":"2020-04-24"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-18721","kev_date_added":null,"published":"2020-04-24"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can perform unauthorized actions on NETGEAR routers via CSRF, requiring firmware upgrades to mitigate.","url":"https://insights.sbomify.com/CVE-2020-26912/"}