# CVE-2024-12019: Arbitrary File Read via Document API

> Authenticated attackers can read arbitrary files on the server via the Document API, exposing sensitive system data.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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:** 14 Mar 2025
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-wqjp-f422-gr32

## What is CVE-2024-12019?

CVE-2024-12019 is a high-severity path traversal vulnerability in LogicalDOC Community, published on 14 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The API used to interact with documents in the application contains a flaw that allows an authenticated attacker to read the contents of files on the underlying operating system. An account with ‘read’ and ‘download’ privileges on at least one existing document in the application is required to exploit the vulnerability. Exploitation of this vulnerability would allow an attacker to read the contents of any file available within the privileges of the system user running the application.

Weakness: CWE-23 (Relative Path Traversal)

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


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

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

## Is CVE-2024-12019 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-12019 is a high-severity path traversal vulnerability in LogicalDOC Community, published on 14 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-12019 in the wild and no public exploit code.

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

## Sources

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

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