{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-20183 exists.","fix":"No fix has been published for CVE-2019-20183 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20183 is a high-severity vulnerability in n/a, published on 9 Jan 2020. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-20183 and fix it if it is affected.\n\nWhat it is: CVE-2019-20183 is a high-severity vulnerability in n/a, published on 9 Jan 2020. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-20183 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-2019-20183/ (Markdown: https://insights.sbomify.com/CVE-2019-20183/index.md)","id":"CVE-2019-20183","markdown":"https://insights.sbomify.com/CVE-2019-20183/index.md","name":"CVE-2019-20183","record":{"aliases":["GHSA-rmg7-3v8w-rm26"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Employee Records System","requires_auth":"high_privilege","summary":"Attackers can upload and execute arbitrary PHP code by bypassing client-side file extension validation in the image upload feature.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"employee_records_system","vendor":"employee_records_system_project"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"uploadimage.php in Employee Records System 1.0 allows upload and execution of arbitrary PHP code because file-extension validation is only on the client side. The attacker can modify global.js to allow the .php extension.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2019/CVE-2019-20183.yaml","stars":null,"title":"Simple Employee Records System 1.0 - Unrestricted File Upload"}],"tier":"weaponised"},"has_fix":null,"headline":"File upload in n/a","id":"CVE-2019-20183","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2019-20184"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-20182"},"products":["n/a"],"published":"2020-01-09","related":[],"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":"MIT","name":"Nuclei templates"}],"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 by bypassing client-side file extension validation in the image upload feature.","url":"https://insights.sbomify.com/CVE-2019-20183/"}