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

> Attackers can exploit a path traversal vulnerability in WebFileSys to access sensitive files outside the intended directory via crafted HTTP requests.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 6 Feb 2025
- **Updated:** 11 Feb 2025
- **Also known as:** GHSA-rrqx-xr4w-7wpj

## What is CVE-2024-53586?

CVE-2024-53586 is a medium-severity path traversal vulnerability in n/a, published on 6 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in the relPath parameter of WebFileSys version 2.31.0 allows attackers to perform directory traversal via a crafted HTTP request. By injecting traversal payloads into the parameter, attackers can manipulate file paths and gain unauthorized access to sensitive files, potentially exposing data outside the intended directory.

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

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


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

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

## Is CVE-2024-53586 being exploited?

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

Public exploit code:

- WebFileSys 2.31.0 - Directory Path Traversal (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-53586 is a medium-severity path traversal vulnerability in n/a, published on 6 Feb 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-53586 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-53586/ (Markdown: https://insights.sbomify.com/CVE-2024-53586/index.md)
```

## Sources

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

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