# CVE-2025-59051: FreePBX Endpoint Manager command injection via Network Scanning feature

> Authenticated attackers can execute arbitrary OS commands via the Network Scanning feature in FreePBX Endpoint Manager.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2025
- **Updated:** 13 Feb 2026

## What is CVE-2025-59051?

CVE-2025-59051 is a high-severity command injection vulnerability in FreePBX endpoint, published on 14 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The FreePBX Endpoint Manager module includes a Network Scanning feature that provides web-based access to nmap functionality for network device discovery. In Endpoint Manager 16 before 16.0.92 and 17 before 17.0.6, insufficiently sanitized user-supplied input allows authenticated OS command execution as the asterisk user. Authentication with a known username is required. Updating to Endpoint Manager 16.0.92 or 17.0.6 addresses the issue.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-59051?


## How do I fix CVE-2025-59051?

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

## Is CVE-2025-59051 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59051 and fix it if it is affected.

What it is: CVE-2025-59051 is a high-severity command injection vulnerability in FreePBX endpoint, published on 14 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59051 in the wild and no public exploit code.

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

## Sources

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

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