{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16287 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16287 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16287 is a critical vulnerability in n/a, published on 14 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-16287 and fix it if it is affected.\n\nWhat it is: CVE-2018-16287 is a critical vulnerability in n/a, published on 14 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-16287 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-16287/ (Markdown: https://insights.sbomify.com/CVE-2018-16287/index.md)","id":"CVE-2018-16287","markdown":"https://insights.sbomify.com/CVE-2018-16287/index.md","name":"CVE-2018-16287","record":{"aliases":["GHSA-7pg5-mv3h-mmc4"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"LG SuperSign CMS","requires_auth":"none","summary":"Attackers can upload malicious files to LG SuperSign CMS via path traversal in upload URIs, potentially leading to remote code execution.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"supersign_cms","vendor":"lg"}],"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":"LG SuperSign CMS allows file upload via signEzUI/playlist/edit/upload/..%2f URIs.","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":"File upload in n/a","id":"CVE-2018-16287","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":"Path traversal in n/a","id":"CVE-2018-16288"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2018-16286"},"products":["n/a"],"published":"2018-09-14","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2018-17173","kev_date_added":null,"published":"2018-09-21"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2018-16286","kev_date_added":null,"published":"2018-09-14"},{"cvss_score":8.6,"headline":"Path traversal in n/a","id":"CVE-2018-16288","kev_date_added":null,"published":"2018-09-14"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2018-16706","kev_date_added":null,"published":"2018-09-14"},{"cvss_score":4.8,"headline":"XSS vulnerability in LG SuperSign CMS","id":"CVE-2024-6177","kev_date_added":null,"published":"2024-06-20"},{"cvss_score":4.8,"headline":"XSS vulnerability in LG SuperSign CMS","id":"CVE-2024-6178","kev_date_added":null,"published":"2024-06-20"}],"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 upload malicious files to LG SuperSign CMS via path traversal in upload URIs, potentially leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2018-16287/"}