# CVE-2024-0849: Leanote 2.7.0 - Local File Read

> Attackers can read arbitrary local files from the server due to a path traversal vulnerability in Leanote.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Feb 2024
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-rpw7-c5cp-v8vp

## What is CVE-2024-0849?

CVE-2024-0849 is a medium-severity path traversal vulnerability in Leanote, published on 7 Feb 2024. 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

Leanote version 2.7.0 allows obtaining arbitrary local files. This is possible because the application is vulnerable to LFR.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-0849?

It affects 1 product.


Products: Leanote Desktop.

## How do I fix CVE-2024-0849?

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

## Is CVE-2024-0849 being exploited?

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

## Other vulnerabilities in Leanote

- [CVE-2017-1000492](https://insights.sbomify.com/CVE-2017-1000492/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0849 and fix it if it is affected.

What it is: CVE-2024-0849 is a medium-severity path traversal vulnerability in Leanote, published on 7 Feb 2024. 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-2024-0849 in the wild and no public exploit code.

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

## Sources

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

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