{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-27387 exists.","fix":"No fix has been published for CVE-2020-27387 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-27387 is a high-severity vulnerability in n/a, published on 5 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-27387 and fix it if it is affected.\n\nWhat it is: CVE-2020-27387 is a high-severity vulnerability in n/a, published on 5 Nov 2020. 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-2020-27387 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-2020-27387/ (Markdown: https://insights.sbomify.com/CVE-2020-27387/index.md)","id":"CVE-2020-27387","markdown":"https://insights.sbomify.com/CVE-2020-27387/index.md","name":"CVE-2020-27387","record":{"aliases":["GHSA-fmrq-56mh-96f5"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"HorizontCMS","requires_auth":"low_privilege","summary":"Authenticated attackers can upload and execute arbitrary PHP code in HorizontCMS by renaming files to have a PHP extension.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"horizontcms","vendor":"horizontcms_project"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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":"An unrestricted file upload issue in HorizontCMS through 1.0.0-beta allows an authenticated remote attacker (with access to the FileManager) to upload and execute arbitrary PHP code by uploading a PHP payload, and then using the FileManager's rename function to provide the payload (which will receive a random name on the server) with the PHP extension, and finally executing the PHP file via an HTTP GET request to /storage/\u003cphp_file_name\u003e. NOTE: the vendor has patched this while leaving the version number at 1.0.0-beta.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-09-24","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2020-09-24","kind":"metasploit","ref":"exploit/multi/http/horizontcms_upload_exec","stars":null,"title":"HorizontCMS Arbitrary PHP File Upload"}],"tier":"weaponised"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2020-27387","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"YOURLS Stored Cross Site Scripting (XSS)","id":"CVE-2020-27388"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2020-27386"},"products":["n/a"],"published":"2020-11-05","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2021-28428","kev_date_added":null,"published":"2022-04-05"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2020-28693","kev_date_added":null,"published":"2020-11-16"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2022-25104","kev_date_added":null,"published":"2022-02-23"}],"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"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Authenticated attackers can upload and execute arbitrary PHP code in HorizontCMS by renaming files to have a PHP extension.","url":"https://insights.sbomify.com/CVE-2020-27387/"}