# CVE-2021-41242: Path Traversal in some REST methods leading to file upload to arbitrary places

> Authenticated attackers can exploit path traversal in REST methods to write files to arbitrary locations, potentially leading to code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **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:** 10 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-62hv-rfp4-hmrm

## What is CVE-2021-41242?

CVE-2021-41242 is a high-severity path traversal vulnerability in OpenOLAT, published on 10 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenOlat is a web-basedlearning management system. A path traversal vulnerability exists in OpenOlat prior to versions 15.5.12 and 16.0.5. By providing a filename that contains a relative path as a parameter in some REST methods, it is possible to create directory structures and write files anywhere on the target system. The attack could be used to write files anywhere in the web root folder or outside, depending on the configuration of the system and the properly configured permission of the application server user. The attack requires an OpenOlat user account, an enabled REST API and the rights on a business object to call the vulnerable REST calls. The problem is fixed in version 15.5.12 and 16.0.5. There is a workaround available. The vulnerability requires the REST module to be enabled. Disabling the REST module or limiting the REST module via some firewall or web-server access rules to be accessed only be trusted systems will mitigate the risk.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2021-41242?

It affects 1 product.


Products: Frentix Openolat.

## How do I fix CVE-2021-41242?

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

## Is CVE-2021-41242 being exploited?

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

## Other vulnerabilities in OpenOLAT

- [CVE-2026-31946](https://insights.sbomify.com/CVE-2026-31946/): OpenOLAT: Authentication bypass via forged JWT in OIDC implicit flow (critical 9.8)
- [CVE-2026-28228](https://insights.sbomify.com/CVE-2026-28228/): OpenOLAT: Server-Side Template Injection (SSTI) in Velocity templates allows Remote Code Execution (high 8.8)
- [CVE-2021-39181](https://insights.sbomify.com/CVE-2021-39181/): Unsafe Deserialization of User Data Using XStream (high 8.8)
- [CVE-2021-39180](https://insights.sbomify.com/CVE-2021-39180/): Path Traversal in Archive Handling Leading to Code Execution (high 8.1)
- [CVE-2021-41152](https://insights.sbomify.com/CVE-2021-41152/): Path Traversal in Folder Component Leading to Local File Inclusion (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41242 and fix it if it is affected.

What it is: CVE-2021-41242 is a high-severity path traversal vulnerability in OpenOLAT, published on 10 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41242 in the wild and no public exploit code.

Affected product: OpenOLAT. 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-2021-41242/ (Markdown: https://insights.sbomify.com/CVE-2021-41242/index.md)
```

## Sources

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

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