# CVE-2025-57819: Sangoma FreePBX Authentication Bypass

> Unauthenticated attackers can bypass authentication to manipulate the database and execute arbitrary code on FreePBX endpoints.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Yes, since 29 Aug 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-m42g-xg4c-5f3h

## What is CVE-2025-57819?

CVE-2025-57819 is a critical authentication bypass vulnerability in Sangoma Freepbx, published on 28 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FreePBX is an open-source web-based graphical user interface. FreePBX 15, 16, and 17 endpoints are vulnerable due to insufficiently sanitized user-supplied data allowing unauthenticated access to FreePBX Administrator leading to arbitrary database manipulation and remote code execution. This issue has been patched in endpoint versions 15.0.66, 16.0.89, and 17.0.3.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

It affects 1 product.


Products: Sangoma Freepbx.

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

No fix has been published for CVE-2025-57819 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 19 Sep 2025.

## Is CVE-2025-57819 being exploited?

Yes. Attackers have exploited CVE-2025-57819 in the wild since at least 29 Aug 2025.

Public exploit code:

- https://github.com/watchtowrlabs/watchTowr-vs-FreePBX-CVE-2025-57819 (github_poc): https://github.com/watchtowrlabs/watchTowr-vs-FreePBX-CVE-2025-57819
- https://github.com/0xEhab/FreePBX-CVE-2025-57819-RCE (github_poc): https://github.com/0xEhab/FreePBX-CVE-2025-57819-RCE
- FreePBX versions 15, 16, and 17 contain a Remote Code Execution (RCE) vulnerability caused by insufficient sanitization of user-supplied data in endpoints. (github_poc): https://github.com/MuhammadWaseem29/SQL-Injection-and-RCE_CVE-2025-57819
- FreePBX SQL Injection Exploit (github_poc): https://github.com/blueisbeautiful/CVE-2025-57819
- CVE-2025-57819 -> rce  (github_poc): https://github.com/b4sh2/CVE-2025-57819-poc
- Detects vulnerable FreePBX versions affected by CVE-2025-57819. (github_poc): https://github.com/cybertechajju/cve-2025-57819

## Other vulnerabilities in Sangoma Freepbx

- [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)
- [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-2025-57819 and fix it if it is affected.

What it is: CVE-2025-57819 is a critical authentication bypass vulnerability in Sangoma Freepbx, published on 28 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-57819 in the wild since at least 29 Aug 2025.

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-2025-57819/ (Markdown: https://insights.sbomify.com/CVE-2025-57819/index.md)
```

## Sources

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

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