# CVE-2026-46376: FreePBX: Unauthenticated Use of Hard-Coded Credentials Vulnerability in FreePBX UCP Interface

> Unauthenticated attackers can access the User Control Panel using hard-coded initial template credentials if the administrator fails to change them after enabling the feature.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-m55x-h47x-v3gx

## What is CVE-2026-46376?

CVE-2026-46376 is a critical vulnerability in Sangoma Freepbx, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FreePBX is an open source IP PBX. From 15.0.42 to before 16.0.45 and 17.0.7, unauthenticated users may be able to access the User Control Panel (UCP) using hard-coded initial template credentials if these were not immediately changed by the Administrator who enabled UCP. Authenticated access to ACP is required for the initial setup of UCP generic templates, but after that, without further steps by the admin, unauthenticated users may be able to gain access. This vulnerability is fixed in 16.0.45 and 17.0.7.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Sangoma Freepbx.

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

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

## Is CVE-2026-46376 being exploited?

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

Public exploit code:

- CVE-2026-46376 - FreePBX Unauthenticated UCP Access via Hard-Coded Credentials (github_poc): https://github.com/portbuster1337/CVE-2026-46376

## 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-2025-66039](https://insights.sbomify.com/CVE-2025-66039/): FreePBX Endpoint Manager Allows Unauthenticated Logins to Administrator Control Panel via Forged Basic Auth Header (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46376 is a critical vulnerability in Sangoma Freepbx, published on 29 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46376 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-46376/ (Markdown: https://insights.sbomify.com/CVE-2026-46376/index.md)
```

## Sources

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

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