{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26174 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26174 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26174 is a high-severity vulnerability in n/a, published on 18 Dec 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-26174 and fix it if it is affected.\n\nWhat it is: CVE-2020-26174 is a high-severity vulnerability in n/a, published on 18 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-26174 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-26174/ (Markdown: https://insights.sbomify.com/CVE-2020-26174/index.md)","id":"CVE-2020-26174","markdown":"https://insights.sbomify.com/CVE-2020-26174/index.md","name":"CVE-2020-26174","record":{"aliases":["GHSA-g862-hhr5-33gv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Business Workflow","requires_auth":"low_privilege","summary":"Attackers can bypass client-side file type restrictions to upload arbitrary files as attachments, potentially leading to code execution or data modification.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"business_workflow","vendor":"tangro"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:L/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"tangro Business Workflow before 1.18.1 requests a list of allowed filetypes from the server and restricts uploads to the filetypes contained in this list. However, this restriction is enforced in the browser (client-side) and can be circumvented. This allows an attacker to upload any file as an attachment to a workitem.","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-26174","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-26175"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-26173"},"products":["n/a"],"published":"2020-12-18","related":[{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2020-26175","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2020-26178","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2020-26171","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2020-26176","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2020-26177","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":4.2,"headline":"Auth bypass in n/a","id":"CVE-2020-26172","kev_date_added":null,"published":"2020-12-18"}],"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 bypass client-side file type restrictions to upload arbitrary files as attachments, potentially leading to code execution or data modification.","url":"https://insights.sbomify.com/CVE-2020-26174/"}