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

> Attackers can perform directory traversal in the File Manager to read or modify files outside the intended directory.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jan 2025
- **Updated:** 20 Mar 2025
- **Also known as:** GHSA-fq9p-pm79-953v

## What is CVE-2024-53537?

CVE-2024-53537 is a critical path traversal vulnerability in n/a, published on 31 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in OpenPanel v0.3.4 to v0.2.1 allows attackers to execute a directory traversal in File Actions of File Manager.

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

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

It affects 1 product.


Products: Openpanel Openpanel.

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

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

## Is CVE-2024-53537 being exploited?

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

Public exploit code:

- OpenPanel 0.3.4 - Directory Traversal (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2024-53584](https://insights.sbomify.com/CVE-2024-53584/): Command injection in n/a (critical 9.8)
- [CVE-2025-25871](https://insights.sbomify.com/CVE-2025-25871/): Privilege escalation in n/a (high 8.0)
- [CVE-2024-53582](https://insights.sbomify.com/CVE-2024-53582/): Path traversal in n/a (high 7.5)
- [CVE-2025-25872](https://insights.sbomify.com/CVE-2025-25872/): Privilege escalation in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53537 is a critical path traversal vulnerability in n/a, published on 31 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53537 in the wild and no public exploit code.

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-53537/ (Markdown: https://insights.sbomify.com/CVE-2024-53537/index.md)
```

## Sources

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

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