# CVE-2024-32162: Path traversal in n/a

> Attackers can delete arbitrary files on the server via path traversal in CMSeasy, potentially compromising system integrity.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 17 Apr 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-p88h-cqcf-h49q

## What is CVE-2024-32162?

CVE-2024-32162 is a medium-severity path traversal vulnerability in n/a, published on 17 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CMSeasy 7.7.7.9 is vulnerable to Arbitrary file deletion.

Weakness: CWE-791 (Incomplete Filtering of Special Elements)

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

It affects 1 product.


Products: Cmseasy Cmseasy.

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

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

## Is CVE-2024-32162 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-34880](https://insights.sbomify.com/CVE-2023-34880/): Path traversal in n/a (critical 9.8)
- [CVE-2021-42643](https://insights.sbomify.com/CVE-2021-42643/): File upload in n/a (high 8.8)
- [CVE-2018-11679](https://insights.sbomify.com/CVE-2018-11679/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2024-34314](https://insights.sbomify.com/CVE-2024-34314/): Path traversal in n/a (high 7.5)
- [CVE-2024-34315](https://insights.sbomify.com/CVE-2024-34315/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-32162 is a medium-severity path traversal vulnerability in n/a, published on 17 Apr 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-32162 exists.

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

## Sources

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

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