# CVE-2024-28880: Path traversal in MosP kintai kanri

> A remote authenticated attacker can exploit a path traversal flaw in MosP kintai kanri to access sensitive product information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A: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:** 27 May 2024
- **Updated:** 2 Aug 2024

## What is CVE-2024-28880?

CVE-2024-28880 is a medium-severity path traversal vulnerability in esMind, LLC MosP kintai kanri, published on 27 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Path traversal vulnerability in MosP kintai kanri V4.6.6 and earlier allows a remote attacker who can log in to the product to obtain sensitive information of the product.

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

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


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

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

## Is CVE-2024-28880 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28880 is a medium-severity path traversal vulnerability in esMind, LLC MosP kintai kanri, published on 27 May 2024. 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-2024-28880 exists.

Affected product: esMind, LLC MosP kintai kanri. 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-28880/ (Markdown: https://insights.sbomify.com/CVE-2024-28880/index.md)
```

## Sources

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

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