# CVE-2024-47071: OSS Endpoint Manager allows unauthorized access to read system files

> Authenticated users can read arbitrary system files via path traversal in the OSS Endpoint Manager module for FreePBX.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Oct 2024
- **Updated:** 13 Feb 2026
- **Also known as:** GHSA-x9wc-qjrc-j7ww

## What is CVE-2024-47071?

CVE-2024-47071 is a medium-severity path traversal vulnerability in FreePBX endpointman, published on 1 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

OSS Endpoint Manager is an endpoint manager module for FreePBX. OSS Endpoint Manager module activation can allow authenticated web users unauthorized access to read system files with the permissions of the webserver process. This vulnerability is fixed in 14.0.4.

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

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


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

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

## Is CVE-2024-47071 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47071 is a medium-severity path traversal vulnerability in FreePBX endpointman, published on 1 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47071 exists.

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

## Sources

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

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