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

> Attackers can exploit a local file inclusion vulnerability in Zenitel AlphaWeb XE to read arbitrary files or execute code.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2025
- **Updated:** 4 Feb 2025
- **Also known as:** GHSA-vcf9-g536-773c

## What is CVE-2024-57785?

CVE-2024-57785 is a medium-severity path traversal vulnerability in n/a, published on 16 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Zenitel AlphaWeb XE v11.2.3.10 was discovered to contain a local file inclusion vulnerability via the component amc_uploads.php.

Weakness: CWE-706 (Use of Incorrectly-Resolved Name or Reference)

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


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

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

## Is CVE-2024-57785 being exploited?

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

Public exploit code:

- https://github.com/s4fv4n/CVE-2024-57785 (github_poc): https://github.com/s4fv4n/CVE-2024-57785

## Fix prompt for AI coding agents

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

What it is: CVE-2024-57785 is a medium-severity path traversal vulnerability in n/a, published on 16 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-57785 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-57785/ (Markdown: https://insights.sbomify.com/CVE-2024-57785/index.md)
```

## Sources

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

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