Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2019-19006: Authentication Bypass in Sangoma FreePBX

Published Nov 21, 2019 · Updated 8 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS9.8Critical · v3.1
EPSS94.5%100th percentile
CISA KEVYesAdded Feb 3, 2026
In the wildActivePer CISA KEV
Vendor
Sangoma Technologies Corporation
IdentifiersCVE-2019-19006CWE-287 · Improper Authentication

CVE-2019-19006 is an improper authentication vulnerability in the Sangoma FreePBX Framework login mechanism. Vulnerable implementations establish a session for the supplied username before completing password verification and remove it only after password-mismatch processing. Insufficient input validation allows an array-valued password parameter to interrupt authentication before session cleanup, leaving an authenticated session for the selected user, including an administrator. A remote attacker can therefore access FreePBX administrative services without valid credentials. The vulnerability has been exploited by INJ3CTOR3 in VoIP compromise and toll-fraud operations.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation exposes the FreePBX administrative interface, allowing unauthorized configuration changes, user management, and access to call records. Observed attack chains used administrative access to execute commands through the Asterisk CLI module, deploy PHP webshells, and retrieve database and SIP credentials. These follow-on actions enable persistent compromise, unauthorized outbound calls, toll fraud, and resale of access to compromised telephony infrastructure. Host-level command execution and persistence are post-exploitation outcomes rather than the authentication bypass itself.

Mitigation

If you can’t patch tonight, do this now.

Restrict the FreePBX administrative interface to trusted management networks or VPN access and remove unnecessary public exposure. If compromise is suspected, isolate the PBX or tightly restrict its network access while preserving evidence. Use carrier-side registration restrictions, destination blocks, spending caps, and anomaly alerts to limit telephony abuse. Monitor for unauthorized administrative activity, web-server processes spawning shells, unexpected configuration access, persistence changes, and abnormal outbound calling. These controls do not replace the vendor fix.

Remediation

Patch, then assume compromise.

Apply the vendor fix for CVE-2019-19006 by upgrading FreePBX Framework to a vendor-confirmed fixed release for the applicable release train. Affected version ceilings are listed as 115.0.16.26, 14.0.13.11, and 13.0.197.13; exact first-fixed versions are not established here. For compromised systems, preserve evidence and rebuild from a clean image or comprehensively remove webshells, unauthorized accounts, scheduled tasks, and other persistence. Rotate exposed telephony, database, application, and host credentials after eradication. Updating alone does not remove an existing compromise.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Sangoma Technologies CorporationFreepbxapplication
FAQ

Frequently asked questions

Is CVE-2019-19006 exploited in the wild?
Yes. As of Nov 14, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Feb 3, 2026.
Is there a public exploit for CVE-2019-19006?
Yes. As of Nov 14, 2026, Mallory has reports of a public exploit for CVE-2019-19006.
Is there a patch for CVE-2019-19006?
Apply the vendor fix for CVE-2019-19006 by upgrading FreePBX Framework to a vendor-confirmed fixed release for the applicable release train. Affected version ceilings are listed as 115.0.16.26, 14.0.13.11, and 13.0.197.13; exact first-fixed versions are not established here.
What products are affected by CVE-2019-19006?
Sangoma Technologies Corporation Freepbx.
How severe is CVE-2019-19006?
CVE-2019-19006 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 94.5% (100th percentile) as of Nov 14, 2026.
Activity feed

Recent activity

28 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+6 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence5Every report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity12Community discussion across Reddit, Mastodon, and other social sources.