{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50709 exists.","fix":"No fix has been published for CVE-2025-50709 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-50709 is a medium-severity vulnerability in n/a, published on 17 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-50709 and fix it if it is affected.\n\nWhat it is: CVE-2025-50709 is a medium-severity vulnerability in n/a, published on 17 Sep 2025. 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-2025-50709 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-50709/ (Markdown: https://insights.sbomify.com/CVE-2025-50709/index.md)","id":"CVE-2025-50709","markdown":"https://insights.sbomify.com/CVE-2025-50709/index.md","name":"CVE-2025-50709","record":{"aliases":["GHSA-hr3c-g4hc-c8wh"],"analysis":{"component_type":"cloud_service","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Perplexity AI GPT-4","requires_auth":"low_privilege","summary":"A remote attacker can obtain sensitive information via a GET parameter in Perplexity AI GPT-4.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-598","name":"Use of HTTP Request With Sensitive Query String"}],"description":"An issue in Perplexity AI GPT-4 allows a remote attacker to obtain sensitive information via a GET parameter","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":"Information disclosure in n/a","id":"CVE-2025-50709","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2025-50722"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2025-50708"},"products":["n/a"],"published":"2025-09-17","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)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-17","vendors":["n/a"]},"summary":"A remote attacker can obtain sensitive information via a GET parameter in Perplexity AI GPT-4.","url":"https://insights.sbomify.com/CVE-2025-50709/"}