Freepbx vulnerabilitiesAnd the versions its exploited flaws hit.
Freepbx is made by Sangoma. We track 28 published vulnerabilities listed under that exact name, across 1,617 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 3 February 2026. Sangoma lists newer releases under their own names, such as Freepbx Linux 7, so check those pages too.
The most recent Freepbx flaw added to the known-exploited list is CVE-2019-19006, on 3 February 2026. We keep watching the known-exploited list.
Is Freepbx listed under other names? Yes.
Sangoma also lists Freepbx under more specific names, such as Freepbx Linux 7. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which versions of Freepbx do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "15.0 to before 15.0.66" means from 15.0 up to, but not including, 15.0.66. Find your version, then patch.
- CVE-2019-19006Exploited list, 3 Feb 2026
Sangoma FreePBX Improper Authentication Vulnerability
13.0.0.0 to 13.0.197.1314.0.0.0 to 14.0.13.1115.0.0.0 to 15.0.16.26 - CVE-2025-57819Exploited list, 29 Aug 2025
Sangoma FreePBX Authentication Bypass Vulnerability
15.0 to before 15.0.6616.0 to before 16.0.8917.0 to before 17.0.3
Which Freepbx vulnerabilities are being exploited?
2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8Sangoma FreePBX Improper Authentication Vulnerability
Sangoma FreePBX contains an improper authentication vulnerability that potentially allows unauthorized users to bypass password authentication and access services provided by the FreePBX admin.
- 9.8Sangoma FreePBX Authentication Bypass Vulnerability
Sangoma FreePBX contains an authentication bypass vulnerability due to insufficiently sanitized user-supplied data allows unauthenticated access to FreePBX Administrator leading to arbitrary database manipulation and...
Which Freepbx flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 95%
FreePBX is an open-source web-based graphical user interface.
- 70%CVE-2012-4869High
The callme_startcall function in recordings/misc/callme_page.php in FreePBX 2.9, 2.10, and earlier allows remote attackers to execute arbitrary commands via the callmenum parameter in a c action.
- 56%
Sangoma FreePBX 115.0.16.26 and below, 14.0.13.11 and below, 13.0.197.13 and below have Incorrect Access Control.
- 52%CVE-2014-1903High
admin/libraries/view.functions.php in FreePBX 2.9 before 2.9.0.14, 2.10 before 2.10.1.15, 2.11 before 2.11.0.23, and 12 before 12.0.1alpha22 does not restrict the set of functions accessible to the API handler, which...
- 43%CVE-2014-7235Critical
htdocs_ari/includes/login.php in the ARI Framework module/Asterisk Recording Interface (ARI) in FreePBX before 2.9.0.9, 2.10.x, and 2.11 before 2.11.1.5 allows remote attackers to execute arbitrary code via the...
- 21%CVE-2021-45461Critical
FreePBX, when restapps (aka Rest Phone Apps) 15.0.19.87, 15.0.19.88, 16.0.18.40, or 16.0.18.41 is installed, allows remote attackers to execute arbitrary code, as exploited in the wild in December 2021.
- 9.4%CVE-2010-3490Medium
Directory traversal vulnerability in page.recordings.php in the System Recordings component in the configuration interface in FreePBX 2.8.0 and earlier allows remote authenticated administrators to create arbitrary...
- 3.1%CVE-2019-19538High
In Sangoma FreePBX 13 through 15 and sysadmin (aka System Admin) 13.0.92 through 15.0.13.6 modules have a Remote Command Execution vulnerability that results in Privilege Escalation.
- 2.2%CVE-2020-10666Critical
The restapps (aka Rest Phone apps) module for Sangoma FreePBX and PBXact 13, 14, and 15 through 15.0.19.2 allows remote code execution via a URL variable to an AMI command.
- 2.2%CVE-2018-6393High
FreePBX 10.13.66-32bit and 14.0.1.24 (SNG7-PBX-64bit-1712-2) allow post-authentication SQL injection via the order parameter.
Running Freepbx? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Sangoma FreePBX contains an improper authentication vulnerability that potentially allows unauthorized users to bypass password authentication and access services provided by the FreePBX admin.
- Matched to
- Freepbx on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 28 published vulnerabilities listed under the name Freepbx, across 1,617 versions. The most recent Freepbx flaw added to the known-exploited list is CVE-2019-19006, on 3 February 2026.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2019-19006 and CVE-2025-57819.
Sangoma also lists Freepbx under more specific names, such as Freepbx Linux 7. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Each flaw names its own versions, usually as ranges. The newest, CVE-2019-19006, affects 13.0.0.0 to 13.0.197.13, 14.0.0.0 to 14.0.13.11, 15.0.0.0 to 15.0.16.26. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Freepbx. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.