Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Sangoma FreePBX Improper Authentication Vulnerability

IdentifiersCVE-2019-19006CWE-287· Improper Authentication

CVE-2019-19006 is an improper authentication / authentication bypass vulnerability in Sangoma FreePBX affecting versions 15.0.16.26 and below, 14.0.13.11 and below, and 13.0.197.13 and below. Available reporting indicates the login flow sets a session for a supplied username before password validation fully completes, and does not properly sanitize the password parameter. By supplying the password parameter as an array element rather than a normal scalar value, an attacker can trigger failure in the authentication function before the session is unset, allowing retention of an authenticated session for an arbitrary chosen user, including the FreePBX administrator. Successful exploitation allows unauthorized access to services exposed through the FreePBX administrative interface.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation can result in full administrative compromise of the FreePBX web interface without valid credentials. An attacker may bypass login, access administrator services, modify PBX configuration, manage users, access call-related data exposed to the admin interface, and use the compromised PBX for further post-exploitation activity. Reporting on in-the-wild abuse links this flaw to campaigns against VoIP infrastructure where attackers obtained admin access and then deployed web shells, harvested credentials/configuration, established persistence, and abused telephony resources for fraud.

Mitigation

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

If immediate patching is not possible, restrict network access to the FreePBX administrative interface to trusted management hosts or VPN-only access, remove direct internet exposure, and monitor for suspicious authentication requests and unexpected admin sessions. Review web roots and FreePBX-related directories for unauthorized PHP files or web shells, inspect for anomalous configuration changes, new privileged accounts, modified SSH access, and abuse of telephony features. These measures are compensating controls only and do not eliminate the underlying authentication bypass.

Remediation

Patch, then assume compromise.

Upgrade Sangoma FreePBX to a fixed release newer than the affected versions: newer than 15.0.16.26, 14.0.13.11, and 13.0.197.13, as applicable to the deployed branch. Apply the vendor-provided fix referenced in the FreePBX advisory / GHSA-85h5-chmw-697j and follow vendor guidance for all supported release trains. Because this vulnerability has been listed in CISA KEV and is known to be actively exploited, exposed systems should be prioritized for immediate patching and post-patch compromise assessment.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence3

Every observed campaign linking this CVE to a named adversary.

Associated malware2

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity12

Community discussion across Reddit, Mastodon, and other social sources.