{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5351 exists.","fix":"No fix has been published for CVE-2026-5351 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5351 is a medium-severity command injection vulnerability in Trendnet TEW-657BRM, published on 2 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5351 and fix it if it is affected.\n\nWhat it is: CVE-2026-5351 is a medium-severity command injection vulnerability in Trendnet TEW-657BRM, published on 2 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5351 exists.\n\nAffected product: Trendnet TEW-657BRM. 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-2026-5351/ (Markdown: https://insights.sbomify.com/CVE-2026-5351/index.md)","id":"CVE-2026-5351","markdown":"https://insights.sbomify.com/CVE-2026-5351/index.md","name":"CVE-2026-5351","record":{"aliases":["GHSA-3w99-p9rf-w2qj"],"analysis":{"component_type":"network_device","fix_type":"end_of_life","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Trendnet wireless router","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary OS commands via the wl_enrolee_pin parameter in the discontinued Trendnet TEW-657BRM router.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"tew-657brm_firmware","vendor":"trendnet"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"},{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"A weakness has been identified in Trendnet TEW-657BRM 1.00.1. This affects the function add_wps_client of the file /setup.cgi. This manipulation of the argument wl_enrolee_pin causes os command injection. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. The vendor confirms, that \"[t]he product in question (...) has been discontinued and end of life since June 23, 2011, that is more than 14 years ago. We no longer provide support for this product, so we are not able to confirm the vulnerabilities. We will make an announcement on our website's product support page and notify customers who registered their products with us.\" This vulnerability only affects products that are no longer supported by the maintainer.","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":"Trendnet TEW-657BRM setup.cgi add_wps_client os command injection","id":"CVE-2026-5351","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Trendnet TEW-657BRM setup.cgi edit os command injection","id":"CVE-2026-5352"},"packages":[],"prev":{"headline":"Trendnet TEW-657BRM setup.cgi update_pcdb stack-based overflow","id":"CVE-2026-5350"},"products":["TEW-657BRM"],"published":"2026-04-02","related":[{"cvss_score":8.7,"headline":"Trendnet TEW-657BRM setup.cgi add_apcdb stack-based overflow","id":"CVE-2026-5349","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":8.7,"headline":"Trendnet TEW-657BRM setup.cgi update_pcdb stack-based overflow","id":"CVE-2026-5350","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":8,"headline":"Command injection in n/a","id":"CVE-2025-65202","kev_date_added":null,"published":"2025-11-26"},{"cvss_score":5.3,"headline":"Trendnet TEW-657BRM setup.cgi edit os command injection","id":"CVE-2026-5352","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":5.3,"headline":"Trendnet TEW-657BRM setup.cgi ping_test os command injection","id":"CVE-2026-5353","kev_date_added":null,"published":"2026-04-02"},{"cvss_score":5.3,"headline":"Trendnet TEW-657BRM setup.cgi vpn_connect os command injection","id":"CVE-2026-5354","kev_date_added":null,"published":"2026-04-02"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-03","vendors":["Trendnet"]},"summary":"Remote attackers can execute arbitrary OS commands via the wl_enrolee_pin parameter in the discontinued Trendnet TEW-657BRM router.","url":"https://insights.sbomify.com/CVE-2026-5351/"}