{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-14911 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-14911 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-14911 is a high-severity vulnerability in n/a, published on 3 Aug 2018. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-14911 and fix it if it is affected.\n\nWhat it is: CVE-2018-14911 is a high-severity vulnerability in n/a, published on 3 Aug 2018. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-14911 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-14911/ (Markdown: https://insights.sbomify.com/CVE-2018-14911/index.md)","id":"CVE-2018-14911","markdown":"https://insights.sbomify.com/CVE-2018-14911/index.md","name":"CVE-2018-14911","record":{"aliases":["GHSA-hw48-8j58-8vvg"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"UKCMS web application","requires_auth":"high_privilege","summary":"An authenticated admin can upload malicious PHP scripts by manipulating file extension settings, leading to remote code execution on the server.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ukcms","vendor":"ukcms"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/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":"A file upload vulnerability exists in ukcms v1.1.7 and earlier. The vulnerability is due to the system not strictly filtering the file upload type. An attacker can exploit the vulnerability to upload a script Trojan to admin.php/admin/configset/index/group/upload.html to gain server control by composing a request for a .txt upload and then changing it to a .php upload. The attacker must have admin access to change the upload_file_ext (aka \"Allow upload file suffix\") setting, and must use \"php,php\" in this setting to bypass the \"php\" restriction.","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-14911","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-14912"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2018-14910"},"products":["n/a"],"published":"2018-08-03","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-10888","kev_date_added":null,"published":"2019-04-05"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2020-18449","kev_date_added":null,"published":"2021-08-12"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2020-20977","kev_date_added":null,"published":"2021-08-12"}],"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-09-17","vendors":["n/a"]},"summary":"An authenticated admin can upload malicious PHP scripts by manipulating file extension settings, leading to remote code execution on the server.","url":"https://insights.sbomify.com/CVE-2018-14911/"}