+44 1865 950 828 Secure Your Business
Actively exploited

CVE-2025-64328 Sangoma FreePBX OS Command Injection Vulnerability

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.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch urgentlyCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 3 Feb 2026.
  • Rated High severity (CVSS 8.6, scored by Vendor).
  • It has been in the catalogue for 276 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

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.

Affected Versions

ProductVersions
FreePBX filestore>= 17.0.2.36, < 17.0.3

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Sangoma FreePBX . Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Vendor Advisories

Regulation

The Compliance Clock

Cyber EssentialsRated high, so if it affects devices in your Cyber Essentials scope, the update must be installed within 14 days of the vendor releasing it.NIS2If exploitation causes a significant incident, essential and important entities owe their CSIRT an early warning within 24 hours and a notification within 72 hours.DORAFinancial entities must classify ICT incidents and send an initial notification for a major incident within strict deadlines, with exploited flaws a common cause.US federal (BOD 22-01)Federal civilian agencies had until 24 Feb 2026 to remediate. A sensible benchmark for everyone else.

General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.

Stay Ahead

More Exploited Sangoma Flaws

Get alerts for SangomaWe email you when a new Sangoma vulnerability is confirmed as exploited. Add more vendors on Threat Watch.

By signing up you agree to receive Threat Watch alerts. Unsubscribe at any time. See our Privacy Policy.

CVE-2026-9586Sangoma Switchvox SQL Injection VulnerabilityAdded 2 Sep 2026CVE-2019-19006 Sangoma FreePBX Improper Authentication VulnerabilityAdded 3 Feb 2026CVE-2025-57819Sangoma FreePBX Authentication Bypass VulnerabilityAdded 29 Aug 2025

All 4 exploited Sangoma vulnerabilities

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2025-64328 and every other exploited flaw on the list.

Check My Exposure
Evidence

Sources

  1. CISA Known Exploited Vulnerabilities catalogue
  2. NVD: CVE-2025-64328
  3. CVE record: CVE-2025-64328
  4. FIRST EPSS
  5. github.com/FreePBX/security-reporting/security/advisories/GHSA-vm9p-46mv-5xvw
  6. github.com/FreePBX/filestore/blob/f0e3983059271efd80b483ec823310ef19a59013/drivers/SSH/testconnectio
  7. freepbx.org/watch-what-we-do-with-security-fixes-%f0%9f%91%80