{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-8939 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-8939 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-8939 is a critical server-side request forgery vulnerability in Progress Whatsup Gold, published on 1 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-8939 and fix it if it is affected.\n\nWhat it is: CVE-2018-8939 is a critical server-side request forgery vulnerability in Progress Whatsup Gold, published on 1 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-8939 in the wild and no public exploit code.\n\nAffected product: Progress Whatsup Gold. 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-2018-8939/ (Markdown: https://insights.sbomify.com/CVE-2018-8939/index.md)","id":"CVE-2018-8939","markdown":"https://insights.sbomify.com/CVE-2018-8939/index.md","name":"CVE-2018-8939","record":{"aliases":["GHSA-wq29-3hm6-r46x"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Network monitoring software","requires_auth":"none","summary":"Attackers can exploit SSRF in WhatsUp Gold to execute remote commands, access unauthorized data, and bypass security controls.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"whatsup_gold","vendor":"progress"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"An SSRF issue was discovered in NmAPI.exe in Ipswitch WhatsUp Gold before 2018 (18.0). Malicious actors can submit specially crafted requests via the NmAPI executable to (1) gain unauthorized access to the WhatsUp Gold system, (2) obtain information about the WhatsUp Gold system, or (3) execute remote commands.","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":"Server-side request forgery in n/a","id":"CVE-2018-8939","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"progress:whatsup_gold","products":["progress:whatsup_gold"],"type":"ssrf","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"XML external entity in n/a","id":"CVE-2018-8940"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2018-8938"},"products":["n/a"],"published":"2018-05-01","related":[{"cvss_score":9.8,"headline":"Progress WhatsUp Gold SQL Injection","id":"CVE-2024-6670","kev_date_added":"2024-09-16","published":"2024-08-29"},{"cvss_score":9.8,"headline":"Progress WhatsUp Gold Path Traversal","id":"CVE-2024-4885","kev_date_added":"2025-03-03","published":"2024-06-25"},{"cvss_score":9.8,"headline":"WhatsUp Gold WriteDataFile Directory Traversal Remote Code Execution Vulnerability","id":"CVE-2024-46909","kev_date_added":null,"published":"2024-12-02"},{"cvss_score":9.8,"headline":"WhatsUp Gold Registry Overwrite Remote Code Execution Vulnerability","id":"CVE-2024-8785","kev_date_added":null,"published":"2024-12-02"},{"cvss_score":9.8,"headline":"WhatsUp Gold getReport Missing Authentication Authentication Bypass Vulnerability","id":"CVE-2024-7763","kev_date_added":null,"published":"2024-10-24"},{"cvss_score":9.8,"headline":"WhatsUp Gold GetStatisticalMonitorList SQL Injection Authentication Bypass Vulnerability","id":"CVE-2024-6671","kev_date_added":null,"published":"2024-08-29"},{"cvss_score":9.8,"headline":"WhatsUp Gold WriteDataFile Directory Traversal Remote Code Execution Vulnerability","id":"CVE-2024-4883","kev_date_added":null,"published":"2024-06-25"}],"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-05","vendors":["n/a"]},"summary":"Attackers can exploit SSRF in WhatsUp Gold to execute remote commands, access unauthorized data, and bypass security controls.","url":"https://insights.sbomify.com/CVE-2018-8939/"}