CVE-2026-73663 FreePBX: Unauthenticated SQL injection in FreePBX missedcall via inbound Caller ID name leads to administrator takeover

Critical 9.3 Published Updated

Unauthenticated attackers can inject SQL via Caller ID names to modify administrator accounts and gain unauthorized remote access to FreePBX systems.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-73663?

CVE-2026-73663 is a critical SQL injection vulnerability in Sangoma Freepbx, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

FreePBX is an open source IP PBX. From 16.0.0 until 16.0.11 and 17.0.4, the FreePBX missedcall module places the inbound Caller ID name from crafted SIP From headers into the missedcalllog INSERT in agi-bin/missedcallnotify.php without escaping or bound parameters. An unauthenticated caller can inject SQL when a monitored extension goes unanswered, corrupting the database and modifying FreePBX administrator accounts to obtain unauthorized remote access. This issue is fixed in versions 16.0.11 and 17.0.4.

Weakness: CWE-89

Which versions are affected by CVE-2026-73663?

It affects 1 product.

Products include Sangoma Freepbx.

How do I fix CVE-2026-73663?

No fix has been published for CVE-2026-73663 yet. Limit exposure of the affected software until one is available.

Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.

Is CVE-2026-73663 being exploited?

There is no known exploitation of CVE-2026-73663 in the wild and no public exploit code.

All Sangoma Freepbx vulnerabilities

Sources

Also known as GHSA-g27h-xf3q-h3rm.

Is CVE-2026-73663 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free