{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50675 exists.","fix":"No fix has been published for CVE-2025-50675 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-50675 is a high-severity vulnerability in n/a, published on 7 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-50675 and fix it if it is affected.\n\nWhat it is: CVE-2025-50675 is a high-severity vulnerability in n/a, published on 7 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50675 exists.\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-2025-50675/ (Markdown: https://insights.sbomify.com/CVE-2025-50675/index.md)","id":"CVE-2025-50675","markdown":"https://insights.sbomify.com/CVE-2025-50675/index.md","name":"CVE-2025-50675","record":{"aliases":["GHSA-j2h6-xj8p-656p"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Bioinformatics software","requires_auth":"low_privilege","summary":"An attacker with user access can replace the uninstaller in the world-writable installation directory to gain administrative privileges when an admin runs it.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"GPMAW 14, a bioinformatics software, has a critical vulnerability related to insecure file permissions in its installation directory. The directory is accessible with full read, write, and execute permissions for all users, allowing unprivileged users to manipulate files within the directory, including executable files like GPMAW3.exe, Fragment.exe, and the uninstaller GPsetup64_17028.exe. An attacker with user-level access can exploit this misconfiguration by replacing or modifying the uninstaller (GPsetup64_17028.exe) with a malicious version. While the application itself runs in the user's context, the uninstaller is typically executed with administrative privileges when an administrator attempts to uninstall the software. By exploiting this flaw, an attacker could gain administrative privileges and execute arbitrary code in the context of the admin, resulting in privilege escalation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-08-05","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-08-05T13:45:33Z","kind":"github_poc","ref":"https://github.com/LukeSec/CVE-2025-50675-GPMAW-Permissions","stars":0,"title":"CVE-2025-50675: Insecure install folder permissions in GPMAW bioinformatics software"}],"tier":"weaponised"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2025-50675","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Null dereference in n/a","id":"CVE-2025-50681"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2025-50674"},"products":["n/a"],"published":"2025-08-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-08-08","vendors":["n/a"]},"summary":"An attacker with user access can replace the uninstaller in the world-writable installation directory to gain administrative privileges when an admin runs it.","url":"https://insights.sbomify.com/CVE-2025-50675/"}