{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26176 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26176 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26176 is a medium-severity missing authorization 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-26176 and fix it if it is affected.\n\nWhat it is: CVE-2020-26176 is a medium-severity missing authorization 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-26176 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-26176/ (Markdown: https://insights.sbomify.com/CVE-2020-26176/index.md)","id":"CVE-2020-26176","markdown":"https://insights.sbomify.com/CVE-2020-26176/index.md","name":"CVE-2020-26176","record":{"aliases":["GHSA-w664-p7q3-cm25"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Business Workflow","requires_auth":"low_privilege","summary":"Attackers can list attachments for any workitem by guessing document IDs due to missing access control checks on the API endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"business_workflow","vendor":"tangro"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AC:L/AV:N/A:N/C:L/I:N/PR:L/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"description":"An issue was discovered in tangro Business Workflow before 1.18.1. No (or broken) access control checks exist on the /api/document/\u003cDocumentID\u003e/attachments API endpoint. Knowing a document ID, an attacker can list all the attachments of a workitem, including their respective IDs. This allows the attacker to gather valid attachment IDs for workitems that do not belong to them.","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":"Missing authorization in n/a","id":"CVE-2020-26176","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-26177"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-26175"},"products":["n/a"],"published":"2020-12-18","related":[{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2020-26174","kev_date_added":null,"published":"2020-12-18"},{"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-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 list attachments for any workitem by guessing document IDs due to missing access control checks on the API endpoint.","url":"https://insights.sbomify.com/CVE-2020-26176/"}