{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8273 exists.","fix":"No fix has been published for CVE-2026-8273 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-8273 is a medium-severity command injection vulnerability in Dlink Dns-320 Firmware, published on 11 May 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-8273 and fix it if it is affected.\n\nWhat it is: CVE-2026-8273 is a medium-severity command injection vulnerability in Dlink Dns-320 Firmware, published on 11 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8273 exists.\n\nAffected product: Dlink Dns-320 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-2026-8273/ (Markdown: https://insights.sbomify.com/CVE-2026-8273/index.md)","id":"CVE-2026-8273","markdown":"https://insights.sbomify.com/CVE-2026-8273/index.md","name":"CVE-2026-8273","record":{"aliases":["GHSA-5jp6-jc7m-x7q9"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"D-Link NAS","requires_auth":"high_privilege","summary":"Remote attackers can execute arbitrary OS commands on D-Link DNS-320 devices via vulnerable CGI scripts, requiring authentication.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"dns-320_firmware","vendor":"dlink"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X","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 D-Link DNS-320 2.06B01. This impacts the function cgi_set_host/cgi_set_ntp/cgi_fan_control/cgi_merge_user of the file /cgi-bin/system_mgr.cgi. This manipulation causes os command injection. It is possible to initiate the attack remotely.","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":"D-Link DNS-320 system_mgr.cgi cgi_merge_user os command injection","id":"CVE-2026-8273","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"dlink:dns-320_firmware","products":["dlink:dns-320_firmware"],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"npitre cramfs-tools Directory cramfsck.c do_directory path traversal","id":"CVE-2026-8274"},"packages":[],"prev":{"headline":"D-Link DNS-320 webfile_mgr.cgi chown os command injection","id":"CVE-2026-8272"},"products":["DNS-320"],"published":"2026-05-11","related":[{"cvss_score":9.8,"headline":"D-Link DNS-320 Device Command Injection","id":"CVE-2020-25506","kev_date_added":"2021-11-03","published":"2021-02-02"},{"cvss_score":9.8,"headline":"D-Link DNS-320 Remote Code Execution","id":"CVE-2019-16057","kev_date_added":"2022-04-15","published":"2019-09-16"},{"cvss_score":9.2,"headline":"D-Link DNS-320/DNS-320LW/DNS-325/DNS-340L account_mgr.cgi cgi_user_add os command injection","id":"CVE-2024-10914","kev_date_added":null,"published":"2024-11-06"},{"cvss_score":9.2,"headline":"D-Link DNS-320/DNS-320LW/DNS-325/DNS-340L account_mgr.cgi cgi_user_add os command injection","id":"CVE-2024-10915","kev_date_added":null,"published":"2024-11-06"},{"cvss_score":6.9,"headline":"D-Link DNS-320/DNS-320LW/DNS-325/DNS-340L HTTP GET Request info.xml information disclosure","id":"CVE-2024-10916","kev_date_added":null,"published":"2024-11-06"},{"cvss_score":6.9,"headline":"D-Link DNS-320 Web Management Interface discovery.cgi information disclosure","id":"CVE-2024-8461","kev_date_added":null,"published":"2024-09-05"},{"cvss_score":6.3,"headline":"D-Link DNS-320 Web Management Interface widget_api.cgi information disclosure","id":"CVE-2024-8460","kev_date_added":null,"published":"2024-09-05"}],"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-05-11","vendors":["D-Link"]},"summary":"Remote attackers can execute arbitrary OS commands on D-Link DNS-320 devices via vulnerable CGI scripts, requiring authentication.","url":"https://insights.sbomify.com/CVE-2026-8273/"}