CVE-2025-64328

KEVSangoma FreePBX OS Command Injection Vulnerability

Description

Sangoma FreePBX Endpoint Manager contains an OS command injection vulnerability that could allow for a post-authentication command injection by an authenticated known user via the testconnection -> check_ssh_connect() function. An attacker can leverage this vulnerability to potentially obtain remote access to the system as an asterisk user.

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. In versions 17.0.2.36 and above before 17.0.3, the filestore module within the Administrative interface is vulnerable to a post-authentication command injection by an authenticated known user via the testconnection -> check_ssh_connect() function. An attacker can leverage this vulnerability to obtain remote access to the system as an asterisk user. This issue is fixed in version 17.0.3.

CVSS 4.0 vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

PublishedNov 7, 2025

Last modifiedJun 17, 2026

Added to KEVFeb 3, 2026

Remediation dueFeb 24, 2026

References

github.com/FreePBX/filestore/blob/f0e3983059271efd80b483ec823310ef19a59013/drivers/SSH/testconnection.phpProduct
github.com/FreePBX/security-reporting/security/advisories/GHSA-vm9p-46mv-5xvwVendor AdvisoryMitigation
freepbx.org/watch-what-we-do-with-security-fixes-%f0%9f%91%80Vendor Advisory
cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-64328Third Party AdvisoryUS Government Resource
fortinet.com/blog/threat-research/unveiling-the-weaponized-web-shell-encystphpExploitThird Party Advisory

0 recent articles mention this CVE

Risk assessment · Critical

Actively exploited. Patch immediately.

Exploitation: Confirmed in the wild (CISA KEV)
Federal remediation deadline: Overdue by 244 days
CVSS: 8.6 HIGH
EPSS (30-day exploit probability): 84.6% · top 1% of all CVEs
Weakness: CWE-78
Attack vector: Network, remotely reachable

Recommended actions

1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
2.Treat as emergency change: patch or isolate internet-facing instances first.
3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.

Assessment is derived automatically from the live signals above; verify against your own asset inventory.