# CVE-2022-36081: Wikmd vulnerable to Local File Enumeration when accessing /list

> Attackers can enumerate server files via path traversal in the /list endpoint, exposing sensitive data in Wikmd.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-w4cf-92x9-v8w2

## What is CVE-2022-36081?

CVE-2022-36081 is a high-severity path traversal vulnerability in Linbreux wikmd, published on 7 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wikmd is a file based wiki that uses markdown. Prior to version 1.7.1, Wikmd is vulnerable to path traversal when accessing `/list/<path:folderpath>` and discloses lists of files located on the server including sensitive data. Version 1.7.1 fixes this issue.

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

## Which versions are affected by CVE-2022-36081?

It affects 1 product.


Products: Wikmd Project Wikmd.

## How do I fix CVE-2022-36081?

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

## Is CVE-2022-36081 being exploited?

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

## Other vulnerabilities in Linbreux wikmd

- [CVE-2022-36080](https://insights.sbomify.com/CVE-2022-36080/): Wikmd Cross-site Scripting vulnerability (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36081 and fix it if it is affected.

What it is: CVE-2022-36081 is a high-severity path traversal vulnerability in Linbreux wikmd, published on 7 Sep 2022. 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-2022-36081 in the wild and no public exploit code.

Affected product: Linbreux wikmd. 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-2022-36081/ (Markdown: https://insights.sbomify.com/CVE-2022-36081/index.md)
```

## Sources

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

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