{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-9080 exists.","fix":"No fix has been published for CVE-2017-9080 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-9080 is a high-severity vulnerability in n/a, published on 19 May 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-9080 and fix it if it is affected.\n\nWhat it is: CVE-2017-9080 is a high-severity vulnerability in n/a, published on 19 May 2017. 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-2017-9080 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-2017-9080/ (Markdown: https://insights.sbomify.com/CVE-2017-9080/index.md)","id":"CVE-2017-9080","markdown":"https://insights.sbomify.com/CVE-2017-9080/index.md","name":"CVE-2017-9080","record":{"aliases":["GHSA-v699-rccr-vgfv"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"SMS gateway application","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary code by uploading a malicious PHP file to the PlaySMS web application.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"playsms","vendor":"playsms"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"PlaySMS 1.4 allows remote code execution because PHP code in the name of an uploaded .php file is executed. sendfromfile.php has a combination of Unrestricted File Upload and Code Injection.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2017-05-21","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2017-05-21","kind":"metasploit","ref":"exploit/multi/http/playsms_filename_exec","stars":null,"title":"PlaySMS sendfromfile.php Authenticated \"Filename\" Field Code Execution"},{"date":"2018-05-08","kind":"exploitdb","ref":"44599","stars":null,"title":"PlaySMS 1.4 - 'sendfromfile.php?Filename' (Authenticated) 'Code Execution (Metasploit)"}],"tier":"weaponised"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2017-9080","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Null dereference in n/a","id":"CVE-2017-9083"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2017-9079"},"products":["n/a"],"published":"2017-05-19","related":[{"cvss_score":9.8,"headline":"PlaySMS Server-Side Template Injection","id":"CVE-2020-8644","kev_date_added":"2021-11-03","published":"2020-02-05"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2022-47034","kev_date_added":null,"published":"2023-02-13"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2021-40373","kev_date_added":null,"published":"2021-09-10"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2017-9101","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2008-5881","kev_date_added":null,"published":"2009-01-09"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2009-0103","kev_date_added":null,"published":"2009-01-09"}],"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code by uploading a malicious PHP file to the PlaySMS web application.","url":"https://insights.sbomify.com/CVE-2017-9080/"}