Sangoma FreePBX 115.0.16.26 and below, 14.0.13.11 and below, 13.0.197.13 and below have Incorrect Access Control.
Affects the admin web interface of current FreePBX and PBXact versions when that interface is reachable from the open internet. The listed fix is FreePBX 13.0.197.14.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 13.0.197.14
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Sangoma FreePBX, an open-source phone system (PBX) platform, is affected by this vulnerability. The flaw is an access control weakness that could allow users to reach functions or data they should not be permitted to access.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Sangoma FreePBX 115.0.16.26 and below, 14.0.13.11 and below, 13.0.197.13 and below have Incorrect Access Control.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- Record last updated
- CISA remediation deadline
Due date for US federal agencies to patch
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- n/a n/a
Version range not reported
References 4
freepbx.org
wiki.freepbx.org
community.freepbx.org
pastebin.com
Questions about CVE-2019-19006
What does this mean?
The admin web interface can be accessed remotely without valid authentication, so an outside party could reach the admin GUI. The advisory describes this as an authentication bypass.Source: community.freepbx.org
Am I affected, and how do I check?
The advisory names FreePBX 115.0.16.26 and below, 14.0.13.11 and below, and 13.0.197.13 and below, plus current PBXact versions. Compare the installed FreePBX version against those ranges, and check whether the admin portal is reachable from outside the network.Source: community.freepbx.org
What should I do about it?
For FreePBX 13, upgrade to 13.0.197.14, which the advisory lists as the fix. The sources provided do not give fixed versions for the 14 or 115 branches, so check the vendor advisory for those.Source: community.freepbx.org
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-02-03, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data