# CVE-2020-20495: Path traversal in n/a

> Attackers can delete arbitrary files in Bludit CMS via the backup plugin's deleteBackup parameter, potentially compromising system integrity.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4p76-vp9g-hmxc

## What is CVE-2020-20495?

CVE-2020-20495 is a critical path traversal vulnerability in n/a, published on 31 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

bludit v3.13.0 contains an arbitrary file deletion vulnerability in the backup plugin via the `deleteBackup' parameter.

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

It affects 1 product.


Products: Bludit Bludit.

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

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

## Is CVE-2020-20495 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-18879](https://insights.sbomify.com/CVE-2020-18879/): File upload in n/a (critical 9.8)
- [CVE-2020-18190](https://insights.sbomify.com/CVE-2020-18190/): Path traversal in n/a (critical 9.1)
- [CVE-2024-24550](https://insights.sbomify.com/CVE-2024-24550/): Bludit - Remote Code Execution (RCE) through File API (high 8.9)
- [CVE-2024-24551](https://insights.sbomify.com/CVE-2024-24551/): Bludit - Remote Code Execution (RCE) through Image API (high 8.9)
- [CVE-2020-20210](https://insights.sbomify.com/CVE-2020-20210/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-20495 is a critical path traversal vulnerability in n/a, published on 31 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-20495 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-20495/ (Markdown: https://insights.sbomify.com/CVE-2020-20495/index.md)
```

## Sources

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

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