# CVE-2018-7654: Path traversal in n/a

> Attackers can read arbitrary files on the server via a path traversal vulnerability in the recording download API.

- **Severity:** Medium 6.5 (`CVSS:3.0/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:** 4 Mar 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-9h5p-wpmp-5g3r

## What is CVE-2018-7654?

CVE-2018-7654 is a medium-severity path traversal vulnerability in n/a, published on 4 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

On 3CX 15.5.6354.2 devices, the parameter "file" in the request "/api/RecordingList/download?file=" allows full access to files on the server via path traversal.

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

## Which versions are affected by CVE-2018-7654?

It affects 1 product.


Products: 3cx 3cx.

## How do I fix CVE-2018-7654?

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

## Is CVE-2018-7654 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-49954](https://insights.sbomify.com/CVE-2023-49954/): SQL injection in n/a (critical 9.8)
- [CVE-2022-28005](https://insights.sbomify.com/CVE-2022-28005/): Path traversal in n/a (critical 9.8)
- [CVE-2021-45490](https://insights.sbomify.com/CVE-2021-45490/): Security feature bypass in n/a (critical 9.1)
- [CVE-2023-29059](https://insights.sbomify.com/CVE-2023-29059/): Supply chain in n/a (high 7.8)
- [CVE-2019-14935](https://insights.sbomify.com/CVE-2019-14935/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7654 and fix it if it is affected.

What it is: CVE-2018-7654 is a medium-severity path traversal vulnerability in n/a, published on 4 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7654 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-2018-7654/ (Markdown: https://insights.sbomify.com/CVE-2018-7654/index.md)
```

## Sources

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

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