# CVE-2020-26513: XML external entity in n/a

> 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.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7qwg-6759-84r6

## What is CVE-2020-26513?

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.

### Official 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.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2020-26513?

It affects 1 product.


Products: Intland Codebeamer.

## How do I fix CVE-2020-26513?

No fix has been published for CVE-2020-26513 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-26513 being exploited?

There is no known exploitation of CVE-2020-26513 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-4296](https://insights.sbomify.com/CVE-2023-4296/): PTC Codebeamer Cross site scripting (high 8.8)
- [CVE-2020-26516](https://insights.sbomify.com/CVE-2020-26516/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-26515](https://insights.sbomify.com/CVE-2020-26515/): Weak cryptography in n/a (high 7.5)
- [CVE-2019-20635](https://insights.sbomify.com/CVE-2019-20635/): Code injection in n/a (medium 6.1)
- [CVE-2020-26517](https://insights.sbomify.com/CVE-2020-26517/): Cross-site scripting in n/a (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26513 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2020-26513 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-26513/ (Markdown: https://insights.sbomify.com/CVE-2020-26513/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26513
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26513
- OSV: https://osv.dev/vulnerability/CVE-2020-26513

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-26513/
Summaries are generated and may contain mistakes; the official description above is the record.