{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5004 exists.","fix":"No fix has been published for CVE-2026-5004 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5004 is a high-severity memory corruption vulnerability in Wavlink WL-WN579X3-C, published on 28 Mar 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-5004 and fix it if it is affected.\n\nWhat it is: CVE-2026-5004 is a high-severity memory corruption vulnerability in Wavlink WL-WN579X3-C, published on 28 Mar 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-5004 exists.\n\nAffected product: Wavlink WL-WN579X3-C. 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-5004/ (Markdown: https://insights.sbomify.com/CVE-2026-5004/index.md)","id":"CVE-2026-5004","markdown":"https://insights.sbomify.com/CVE-2026-5004/index.md","name":"CVE-2026-5004","record":{"aliases":["GHSA-xcxj-mq5h-26p9"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Wavlink router","requires_auth":"low_privilege","summary":"Remote attackers can trigger a stack-based buffer overflow in the UPNP handler of Wavlink routers, potentially leading to arbitrary code execution.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"wl-wn579x3-c_firmware","vendor":"wavlink"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"},{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A vulnerability was determined in Wavlink WL-WN579X3-C 231124. This impacts the function sub_4019FC of the file /cgi-bin/firewall.cgi of the component UPNP Handler. Executing a manipulation of the argument UpnpEnabled can lead to stack-based buffer overflow. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.","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":"Wavlink WL-WN579X3-C UPNP firewall.cgi sub_4019FC stack-based overflow","id":"CVE-2026-5004","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Stored XSS in Twiser's OKRs \u0026 Goals","id":"CVE-2026-5005"},"packages":[],"prev":{"headline":"PromtEngineer localGPT Web api_server.py handle_index information disclosure","id":"CVE-2026-5003"},"products":["WL-WN579X3-C"],"published":"2026-03-28","related":[{"cvss_score":8.7,"headline":"Wavlink WL-WN579X3-C firewall.cgi sub_40139C stack-based overflow","id":"CVE-2026-3715","kev_date_added":null,"published":"2026-03-08"},{"cvss_score":4.8,"headline":"Wavlink WL-WN579X3-C adm.cgi sub_401AD4 cross site scripting","id":"CVE-2026-3716","kev_date_added":null,"published":"2026-03-08"}],"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":"total"},"state":"PUBLISHED","updated":"2026-03-30","vendors":["Wavlink"]},"summary":"Remote attackers can trigger a stack-based buffer overflow in the UPNP handler of Wavlink routers, potentially leading to arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2026-5004/"}