# CVE-2025-8729: MigoXLab LMeterX upload_service.py process_cert_files path traversal

> Remote attackers can exploit a path traversal vulnerability in LMeterX to read or modify files via the task_id parameter.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 8 Aug 2025
- **Updated:** 8 Aug 2025
- **Also known as:** GHSA-3x36-997r-xj57

## What is CVE-2025-8729?

CVE-2025-8729 is a medium-severity path traversal vulnerability in MigoXLab LMeterX, published on 8 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in MigoXLab LMeterX 1.2.0 and classified as critical. Affected by this vulnerability is the function process_cert_files of the file backend/service/upload_service.py. The manipulation of the argument task_id leads to path traversal. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier of the patch is f1b00597e293d09452aabd4fa57f3185207350e8. It is recommended to apply a patch to fix this issue.

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

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

It affects 1 product.


Products: Migoxlab Lmeterx.

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

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

## Is CVE-2025-8729 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8729 is a medium-severity path traversal vulnerability in MigoXLab LMeterX, published on 8 Aug 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-8729 exists.

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

## Sources

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

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