# CVE-2025-1228: olajowon Loggrove Logfile Update page path traversal

> Remote attackers can exploit a path traversal vulnerability in the Loggrove logfile update handler to read arbitrary files.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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:** 12 Feb 2025
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-xp5v-36w8-hwxm

## What is CVE-2025-1228?

CVE-2025-1228 is a medium-severity path traversal vulnerability in olajowon Loggrove, published on 12 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as problematic has been found in olajowon Loggrove up to e428fac38cc480f011afcb1d8ce6c2bad378ddd6. Affected is an unknown function of the file /read/?page=1&logfile=LOG_Monitor of the component Logfile Update Handler. The manipulation of the argument path leads to path traversal. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.

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

## Which versions are affected by CVE-2025-1228?


## How do I fix CVE-2025-1228?

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

## Is CVE-2025-1228 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1228 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1228 and fix it if it is affected.

What it is: CVE-2025-1228 is a medium-severity path traversal vulnerability in olajowon Loggrove, published on 12 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1228 exists.

Affected product: olajowon Loggrove. 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-2025-1228/ (Markdown: https://insights.sbomify.com/CVE-2025-1228/index.md)
```

## Sources

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

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