{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-21359 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-21359 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-21359 is a critical vulnerability in n/a, published on 11 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-21359 and fix it if it is affected.\n\nWhat it is: CVE-2020-21359 is a critical vulnerability in n/a, published on 11 Aug 2021. 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-2020-21359 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-21359/ (Markdown: https://insights.sbomify.com/CVE-2020-21359/index.md)","id":"CVE-2020-21359","markdown":"https://insights.sbomify.com/CVE-2020-21359/index.md","name":"CVE-2020-21359","record":{"aliases":["GHSA-r72h-j3wg-jrp4"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Maccms10 CMS","requires_auth":"none","summary":"Attackers can upload malicious files to Maccms10 by bypassing suffix checks, leading to arbitrary code execution on the server.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"maccms","vendor":"maccms"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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 arbitrary file upload vulnerability in the Template Upload function of Maccms10 allows attackers bypass the suffix whitelist verification to execute arbitrary code via adding a character to the end of the uploaded file's name.","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-2020-21359","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 scripting in n/a","id":"CVE-2020-21362"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-21358"},"products":["n/a"],"published":"2021-08-11","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2021-45786","kev_date_added":null,"published":"2022-03-16"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2017-17733","kev_date_added":null,"published":"2017-12-18"},{"cvss_score":9.1,"headline":"Server-side request forgery in n/a","id":"CVE-2025-28089","kev_date_added":null,"published":"2025-03-28"},{"cvss_score":9.1,"headline":"Server-side request forgery in n/a","id":"CVE-2025-28090","kev_date_added":null,"published":"2025-03-28"},{"cvss_score":9.1,"headline":"Server-side request forgery in n/a","id":"CVE-2025-28091","kev_date_added":null,"published":"2025-03-28"},{"cvss_score":8.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-47872","kev_date_added":null,"published":"2023-02-01"}],"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 upload malicious files to Maccms10 by bypassing suffix checks, leading to arbitrary code execution on the server.","url":"https://insights.sbomify.com/CVE-2020-21359/"}