CVE-2025-67722: Authenticated amportal search for ‘freepbx_engine’ in non root writeable directories leads to potential privilege escalation
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 freepbxengine 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 freepbxengine 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 livedangerously = 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-67722?
CVE-2025-67722 is classified as a high severity vulnerability due to its potential for local privilege escalation.
How do I fix CVE-2025-67722?
To fix CVE-2025-67722, upgrade to FreePBX version 16.0.45 or later for 16.x and to 17.0.24 or later for 17.x.
What is the impact of CVE-2025-67722?
The impact of CVE-2025-67722 allows authenticated users to escalate their privileges locally within the FreePBX environment.
Which versions of FreePBX are affected by CVE-2025-67722?
FreePBX versions prior to 16.0.45 and 17.0.24 are affected by CVE-2025-67722.
Is CVE-2025-67722 a remote vulnerability?
No, CVE-2025-67722 is not a remote vulnerability; it requires authenticated local access to exploit.