Quick answers
- Is CVE-2026-73663 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73663 being exploited in the wild.
- How severe is CVE-2026-73663?
- Informational severity, published 13 August 2026.
- Which products and versions are affected?
- FreePBX Missed Call Module 16.0.0 to 16.0.10, 17.0.0 to 17.0.3.
- Is there a fix for CVE-2026-73663?
- A patch was published on 2026-08-13: Versions 16.0.11 and 17.0.4 include fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-73663 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-73663?
- Check whether you run FreePBX Missed Call Module at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an unauthenticated SQL injection flaw in the FreePBX Missed Call module, specifically in the agi-bin/missedcallnotify.php file. The inbound Caller ID name from SIP From headers is inserted directly into a missedcalllog SQL INSERT statement without escaping or using parameterized queries. An unauthenticated attacker can trigger the injection when a monitored extension goes unanswered by crafting a malicious Caller ID name in the SIP message. The attacker can execute arbitrary SQL commands to corrupt the database and modify FreePBX administrator account credentials. The vulnerability affects versions 16.0.0 through 16.0.11 and 17.0.4, with patches available in 16.0.11 and 17.0.4.
Affected products
- FreePBX Missed Call Module 16.0.0 to 16.0.10, 17.0.0 to 17.0.3
Timeline
- 2026-08-13: disclosed
- 2026-08-13: patched: Versions 16.0.11 and 17.0.4 include fix