# CVE-2020-37078: i-doit Open Source CMDB 1.14.1 - Arbitrary File Deletion

> Authenticated attackers can delete arbitrary files on the server via the import module in i-doit Open Source CMDB.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-rrwv-g6g5-vj2p

## What is CVE-2020-37078?

CVE-2020-37078 is a high-severity path traversal vulnerability in i-doit Open Source CMDB, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

i-doit Open Source CMDB 1.14.1 contains a file deletion vulnerability in the import module that allows authenticated attackers to delete arbitrary files by manipulating the delete_import parameter. Attackers can send a POST request to the import module with a crafted filename to remove files from the server's filesystem.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2020-37078 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37078 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2020-37078 is a high-severity path traversal vulnerability in i-doit Open Source CMDB, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37078 exists.

Affected product: i-doit Open Source CMDB. 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-37078/ (Markdown: https://insights.sbomify.com/CVE-2020-37078/index.md)
```

## Sources

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

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