# CVE-2026-45562: FreePBX: Authenticated Remote Code Execution in FreePBX Music on Hold (MoH) Module

> Authenticated attackers can execute arbitrary system commands via unsanitized input in the Music on Hold module, requiring an administrator account.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-4g6v-whq9-944g

## What is CVE-2026-45562?

CVE-2026-45562 is a high-severity command injection vulnerability in Sangoma Freepbx, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FreePBX is an open source IP PBX. Prior to versions 16.0.4 and 17.0.6, the FreePBX Music on Hold (MoH) module contains a critical security flaw that allows authenticated attackers to execute arbitrary system commands with the privileges of the Asterisk service. Authentication with an existing FreePBX administrator account is required. The root cause lies in the fact that the module accepts a POST parameter that defines a custom Asterisk application, which is then stored in the database without any sanitization. Later, this data is written directly to the musiconhold_additional.conf configuration file without validation. Since Asterisk reads this configuration file and executes the specified application, an attacker can inject arbitrary commands that will be executed with Asterisk's permissions. This issue has been patched in versions 16.0.4 and 17.0.6.

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

## Which versions are affected by CVE-2026-45562?

It affects 1 product.


Products: Sangoma Freepbx.

## How do I fix CVE-2026-45562?

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

## Is CVE-2026-45562 being exploited?

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

## Other vulnerabilities in Sangoma Freepbx

- [CVE-2025-57819](https://insights.sbomify.com/CVE-2025-57819/): Sangoma FreePBX Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2019-19006](https://insights.sbomify.com/CVE-2019-19006/): Sangoma FreePBX Improper Authentication (critical 9.8, exploited in the wild)
- [CVE-2026-73663](https://insights.sbomify.com/CVE-2026-73663/): FreePBX: Unauthenticated SQL injection in FreePBX missedcall via inbound Caller ID name leads to administrator takeover (critical 9.3)
- [CVE-2026-73665](https://insights.sbomify.com/CVE-2026-73665/): FreePBX UCP: Unauthenticated remote code execution via socket.io namespace auth bypass and AMI action injection (critical 9.3)
- [CVE-2026-46376](https://insights.sbomify.com/CVE-2026-46376/): FreePBX: Unauthenticated Use of Hard-Coded Credentials Vulnerability in FreePBX UCP Interface (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45562 and fix it if it is affected.

What it is: CVE-2026-45562 is a high-severity command injection vulnerability in Sangoma Freepbx, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45562 in the wild and no public exploit code.

Affected product: Sangoma Freepbx. 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-2026-45562/ (Markdown: https://insights.sbomify.com/CVE-2026-45562/index.md)
```

## Sources

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

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