{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-20670 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-20670 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-20670 is a high-severity vulnerability in n/a, published on 13 Sep 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-20670 and fix it if it is affected.\n\nWhat it is: CVE-2020-20670 is a high-severity vulnerability in n/a, published on 13 Sep 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-20670 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-2020-20670/ (Markdown: https://insights.sbomify.com/CVE-2020-20670/index.md)","id":"CVE-2020-20670","markdown":"https://insights.sbomify.com/CVE-2020-20670/index.md","name":"CVE-2020-20670","record":{"aliases":["GHSA-w2gx-ph96-cxcc"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ZKEACMS","requires_auth":"none","summary":"Attackers can execute arbitrary code by uploading a crafted HTML file to the media upload endpoint in ZKEACMS.","user_interaction":"required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"zkeacms","vendor":"zkea"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 arbitrary file upload vulnerability in /admin/media/upload of ZKEACMS V3.2.0 allows attackers to execute arbitrary code via a crafted HTML file.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2020-20670","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-20671"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2020-20665"},"products":["n/a"],"published":"2021-09-13","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-52239","kev_date_added":null,"published":"2025-08-04"},{"cvss_score":5.4,"headline":"Cross-site Scripting in ZKEACMS","id":"CVE-2022-29362","kev_date_added":null,"published":"2022-05-25"},{"cvss_score":5.3,"headline":"SeriaWei ZKEACMS Event Action System PendingTaskController.cs Edit server-side request forgery","id":"CVE-2025-10764","kev_date_added":null,"published":"2025-09-21"},{"cvss_score":5.3,"headline":"SeriaWei ZKEACMS EventViewerController.cs Download path traversal","id":"CVE-2025-10766","kev_date_added":null,"published":"2025-09-21"},{"cvss_score":5.3,"headline":"ZKEACMS MediaController.cs Proxy server-side request forgery","id":"CVE-2025-10471","kev_date_added":null,"published":"2025-09-15"},{"cvss_score":5.1,"headline":"SeriaWei ZKEACMS SEOSuggestions ZKEACMS.SEOSuggestions.dll server-side request forgery","id":"CVE-2025-10765","kev_date_added":null,"published":"2025-09-21"}],"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-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code by uploading a crafted HTML file to the media upload endpoint in ZKEACMS.","url":"https://insights.sbomify.com/CVE-2020-20670/"}