dbcve.org
FreepbxApplication · Sangoma

CVE-2025-67722

HIGH · 7.8 CVSS v3.1 Published 2025-12-16
Fix available
A fix is available. Upgrade to 16.0.45 / 17.0.24 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In FreePBX versions prior to 16.0.45 and 17.0.24, the deprecated `amportal` startup script searches for and executes a `freepbx_engine` file from `/etc/asterisk/` directories. Since these directories are typically writable by the asterisk user and group members, an authenticated user with asterisk group membership can place a malicious `freepbx_engine` file that will be executed with root privileges when amportal runs.

MitigationUpgrade to FreePBX version 16.0.45 or 17.0.24. Additionally, audit asterisk group membership, inspect /etc/asterisk/ for suspicious files, verify live_dangerously=no in asterisk.conf, and remove unsafe dialplan applications like System() and FILE().

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FreepbxApplication
Affected:>= 16.0, < 16.0.45>= 17.0, < 17.0.24

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check FreePBX version
    Run 'fwconsole ma list' or check /etc/freepbx.conf for the version string
    Affected if Version is >= 16.0 but < 16.0.45, or >= 17.0 but < 17.0.24
  2. Verify amportal script presence
    Check if /usr/local/sbin/amportal or /usr/sbin/amportal exists and is executable
    Affected if The amportal script exists on the system (it is the deprecated component that performs the vulnerable file search)
  3. Inspect asterisk group membership
    Run 'getent group asterisk' or 'grep asterisk /etc/group' to list members
    Affected if Any user account other than root and intended administrators belongs to the asterisk group (these users can write to /etc/asterisk/ and trigger the vulnerability)
  4. Check /etc/asterisk/ directory permissions
    Run 'ls -la /etc/asterisk/' and examine group write permissions
    Affected if The asterisk user or asterisk group has write permission to /etc/asterisk/ or its subdirectories
  5. Scan for freepbx_engine files in /etc/asterisk/
    Run 'find /etc/asterisk/ -name freepbx_engine' and verify any found files are legitimate
    Affected if A freepbx_engine file exists in any /etc/asterisk/ subdirectory (this file would be executed with root privileges by amportal)

You are affected if your FreePBX version is below 16.0.45 or 17.0.24 AND the amportal script exists AND untrusted users have asterisk group membership AND the /etc/asterisk/ directory is writable by the asterisk group.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 16.0.45 / 17.0.24 or later
Fixed in 16.0.4517.0.24
Interim mitigation

Upgrade to FreePBX version 16.0.45 or 17.0.24. Additionally, audit asterisk group membership, inspect /etc/asterisk/ for suspicious files, verify live_dangerously=no in asterisk.conf, and remove unsafe dialplan applications like System() and FILE().

Recommended fix High confidence

FreePBX 16.0.45 or 17.0.24

  1. Upgrade FreePBX to version 16.0.45 or 17.0.24 to obtain the security fix
  2. After upgrading, audit all files in /etc/asterisk/ for any suspicious or unexpected files (especially freepbx_engine)
  3. Review membership of the asterisk group and remove any untrusted users
  4. Verify that 'live_dangerously = no' is set in /etc/asterisk/asterisk.conf
  5. Audit Asterisk dialplan for unsafe applications (System(), FILE(), shell(), etc.) that could manipulate the filesystem
Caveat Minor version upgrade within same major release; review FreePBX module compatibility after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Freepbx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67722 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67722 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data