{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16370 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16370 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16370 is a critical vulnerability in n/a, published on 3 Sep 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-16370 and fix it if it is affected.\n\nWhat it is: CVE-2018-16370 is a critical vulnerability in n/a, published on 3 Sep 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-16370 in the wild and no public exploit code.\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-2018-16370/ (Markdown: https://insights.sbomify.com/CVE-2018-16370/index.md)","id":"CVE-2018-16370","markdown":"https://insights.sbomify.com/CVE-2018-16370/index.md","name":"CVE-2018-16370","record":{"aliases":["GHSA-fv96-f45h-hpj6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PESCMS Team","requires_auth":"none","summary":"Attackers can upload and execute arbitrary PHP code via a ZIP archive in PESCMS Team, leading to remote code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pescms_team","vendor":"pescms"}],"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-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"In PESCMS Team 2.2.1, attackers may upload and execute arbitrary PHP code through /Public/?g=Team\u0026m=Setting\u0026a=upgrade by placing a .php file in a ZIP archive.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2018-09-06","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-09-06T01:52:47Z","kind":"github_poc","ref":"https://github.com/snappyJack/CVE-2018-16370","stars":0,"title":"In PESCMS Team 2.2.1, attackers may upload and execute arbitrary PHP code through  /Public/?g=Team\u0026m=Setting\u0026a=upgrade by placing a .php file in a ZIP archive."}],"tier":"poc_unverified"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2018-16370","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-16371"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-16369"},"products":["n/a"],"published":"2018-09-03","related":[{"cvss_score":6.5,"headline":"Cross-site request forgery in n/a","id":"CVE-2021-31677","kev_date_added":null,"published":"2022-07-06"},{"cvss_score":6.5,"headline":"Cross-site request forgery in n/a","id":"CVE-2021-31678","kev_date_added":null,"published":"2022-07-06"},{"cvss_score":6.5,"headline":"Cross-site request forgery in n/a","id":"CVE-2021-31679","kev_date_added":null,"published":"2022-07-06"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2021-31676","kev_date_added":null,"published":"2022-07-06"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-28092","kev_date_added":null,"published":"2020-11-17"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-16371","kev_date_added":null,"published":"2018-09-03"}],"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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can upload and execute arbitrary PHP code via a ZIP archive in PESCMS Team, leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2018-16370/"}