# CVE-2025-67722: Privilege escalation in framework

> Authenticated local attackers in the asterisk group can escalate privileges to root by placing a malicious file in a writable directory executed by amportal.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-p42w-v77m-hfp8

## What is CVE-2025-67722?

CVE-2025-67722 is a medium-severity vulnerability in Sangoma Freepbx, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

FreePBX is an open-source web-based graphical user interface (GUI) that manages Asterisk. Prior to versions 16.0.45 and 17.0.24 of the FreePBX framework, an authenticated local privilege escalation exists in the deprecated FreePBX startup script `amportal`. In the deprecated `amportal` utility, the lookup for the `freepbx_engine` file occurs in `/etc/asterisk/` directories. Typically, these are configured by FreePBX as writable by the **asterisk** user and any members of the **asterisk** group. This means that a member of the **asterisk** group can add their own `freepbx_engine` file in `/etc/asterisk/` and upon `amportal` executing, it would exec that file with root permissions (even though the file was created and placed by a non-root user). Version 16.0.45 and 17.0.24 contain a fix for the issue. Other mitigation strategies are also available. Confirm only trusted local OS system users are members of the `asterisk` group. Look for suspicious files in the `/etc/asterisk/` directory (via Admin -> Config Edit in the GUI, or via CLI). Double-check that `live_dangerously = no` is set (or unconfigured, as the default is **no**) in `/etc/asterisk/asterisk.conf` file. Eliminate any unsafe custom use of Asterisk dial plan applications and functions that potentially can manipulate the file system, e.g., System(), FILE(), etc.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 1 product.


Products: Sangoma Freepbx.

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

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

## Is CVE-2025-67722 being exploited?

There is no known exploitation of CVE-2025-67722 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-2025-67722 and fix it if it is affected.

What it is: CVE-2025-67722 is a medium-severity vulnerability in Sangoma Freepbx, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67722 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-2025-67722/ (Markdown: https://insights.sbomify.com/CVE-2025-67722/index.md)
```

## Sources

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

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