{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-6710 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-6710 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-6710 is a high-severity vulnerability in n/a, published on 7 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-6710 and fix it if it is affected.\n\nWhat it is: CVE-2019-6710 is a high-severity vulnerability in n/a, published on 7 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-6710 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-2019-6710/ (Markdown: https://insights.sbomify.com/CVE-2019-6710/index.md)","id":"CVE-2019-6710","markdown":"https://insights.sbomify.com/CVE-2019-6710/index.md","name":"CVE-2019-6710","record":{"aliases":["GHSA-2fq9-5c52-qvcp"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Zyxel wireless router","requires_auth":"none","summary":"Attackers can perform unauthorized actions on Zyxel NBG-418N routers via CSRF in login.cgi, potentially taking over accounts.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nbg-418n_firmware","vendor":"zyxel"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Zyxel NBG-418N v2 v1.00(AAXM.4)C0 devices allow login.cgi CSRF.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-01-24","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-01-24","kind":"exploitdb","ref":"46240","stars":null,"title":"Zyxel NBG-418N v2 Modem 1.00(AAXM.6)C0 - Cross-Site Request Forgery"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-6710","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2019-6713"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2019-6708"},"products":["n/a"],"published":"2019-03-07","related":[{"cvss_score":8.1,"headline":"Hardcoded credentials in n/a","id":"CVE-2015-7283","kev_date_added":null,"published":"2015-12-31"},{"cvss_score":7.5,"headline":"Cross-site scripting in NBG-418N v2 firmware","id":"CVE-2023-22921","kev_date_added":null,"published":"2023-05-01"},{"cvss_score":7.5,"headline":"Memory corruption in NBG-418N v2 firmware","id":"CVE-2023-22922","kev_date_added":null,"published":"2023-05-01"},{"cvss_score":6.5,"headline":"Other in NBG-418N v2 firmware","id":"CVE-2023-22923","kev_date_added":null,"published":"2023-05-01"},{"cvss_score":6.1,"headline":"Cross-site scripting in NBG-418N v2 firmware","id":"CVE-2022-45441","kev_date_added":null,"published":"2023-02-07"},{"cvss_score":4.9,"headline":"Memory corruption in NBG-418N v2 firmware","id":"CVE-2023-22924","kev_date_added":null,"published":"2023-05-01"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can perform unauthorized actions on Zyxel NBG-418N routers via CSRF in login.cgi, potentially taking over accounts.","url":"https://insights.sbomify.com/CVE-2019-6710/"}