{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26513 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26513 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26513 is a medium-severity vulnerability in n/a, published on 7 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-26513 and fix it if it is affected.\n\nWhat it is: CVE-2020-26513 is a medium-severity vulnerability in n/a, published on 7 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-26513 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-26513/ (Markdown: https://insights.sbomify.com/CVE-2020-26513/index.md)","id":"CVE-2020-26513","markdown":"https://insights.sbomify.com/CVE-2020-26513/index.md","name":"CVE-2020-26513","record":{"aliases":["GHSA-7qwg-6759-84r6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ALM software","requires_auth":"none","summary":"Attackers can exploit insecure XML parsing in Intland codeBeamer ALM to perform XML External Entity attacks, potentially reading sensitive data or causing denial of service.","user_interaction":"required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"codebeamer","vendor":"intland"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"An issue was discovered in Intland codeBeamer ALM 10.x through 10.1.SP4. The ReqIF XML data, used by the codebeamer ALM application to import projects, is parsed by insecurely configured software components, which can be abused for XML External Entity Attacks.","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":"XML external entity in n/a","id":"CVE-2020-26513","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xxe","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2020-26515"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2020-26511"},"products":["n/a"],"published":"2020-12-07","related":[{"cvss_score":8.8,"headline":"PTC Codebeamer Cross site scripting","id":"CVE-2023-4296","kev_date_added":null,"published":"2023-08-29"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-26516","kev_date_added":null,"published":"2021-06-08"},{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2020-26515","kev_date_added":null,"published":"2021-06-08"},{"cvss_score":6.1,"headline":"Code injection in n/a","id":"CVE-2019-20635","kev_date_added":null,"published":"2020-04-02"},{"cvss_score":4.8,"headline":"Cross-site scripting in n/a","id":"CVE-2020-26517","kev_date_added":null,"published":"2021-06-08"},{"cvss_score":4.8,"headline":"Cross-site scripting in n/a","id":"CVE-2019-19912","kev_date_added":null,"published":"2020-03-30"}],"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 exploit insecure XML parsing in Intland codeBeamer ALM to perform XML External Entity attacks, potentially reading sensitive data or causing denial of service.","url":"https://insights.sbomify.com/CVE-2020-26513/"}