CVE-2025-67722: FreePBX framework · Untrusted Search Path
Affects FreePBX frameworkSource CVE Database V5
Not known to be exploited · CVSS 5.7 Medium : upgrade to 16.0.45 when convenient.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 16.0.45
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:UExploitation evidence
Disclosed: evidence found.
CVE published 16 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade freepbx/framework to 16.0.45.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubfreepbx/frameworkpkg:github/freepbx/frameworkOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Upgrade FreePBX framework to version 16.0.45, 17.0.24, or later where the vulnerability is fixed.
- Restrict membership of the 'asterisk' group strictly to trusted system administrators and service accounts; remove unnecessary users.
- Regularly audit the /etc/asterisk/ directory for unauthorized or suspicious files, especially any 'freepbx_engine' files.
- Verify that the 'live_dangerously' setting in /etc/asterisk/asterisk.conf is set to 'no' or left unconfigured (default is 'no') to prevent unsafe operations.
- Avoid or carefully review custom dial plan applications and functions that can manipulate the filesystem, such as System(), FILE(), and similar calls, to reduce attack surface.
- Implement strict local access controls and monitoring to detect unauthorized group membership changes or file modifications.
- Consider disabling or removing the deprecated 'amportal' script if it is no longer required.
- Employ host-based intrusion detection systems (HIDS) to monitor critical directories and binaries for unauthorized changes.
- Educate administrators on the risks of untrusted search paths and the importance of secure file permissions in telephony systems.
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.