CVE-2026-73663: FreePBX missedcall · SQL Injection
Affects FreePBX missedcallSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 17.0.4 or 16.0.11 as a priority.
Data as of 10 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 17.0.4, 16.0.11
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade missedcall and freepbx/missedcall to 17.0.4 or 16.0.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FreePBXmissedcall | Affected
| Fixed in
|
| FreePBXmissedcall | Affected
| Fixed in
|
GitHubfreepbx/missedcallpkg:github/freepbx/missedcallOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in FreePBX missedcall module versions 16.0.11 and 17.0.4. Users should upgrade to at least these versions to remediate the issue. No other mitigation or temporary workaround is indicated.
Description
FreePBX missedcall module versions from 16.0.0 up to but not including 16.0.11 and from 17.0.0 up to but not including 17.0.4 contain an SQL injection vulnerability. The vulnerability arises because inbound Caller ID names from crafted SIP From headers are inserted into the missedcalllog database without proper escaping or use of bound parameters. This allows an unauthenticated attacker to inject SQL commands when a monitored extension goes unanswered, potentially corrupting the database and modifying administrator accounts to gain unauthorized remote access. The issue is fixed in versions 16.0.11 and 17.0.4.