CVE-2026-73663 FreePBX CVE debrief

Who should care

FreePBX administrators, security teams, and IT professionals responsible for maintaining and securing FreePBX installations should assess exposure and apply patches to prevent potential database corruption and unauthorized remote access. They should also review FreePBX configuration, monitor for suspicious activity, and implement additional security measures to prevent SQL injection attacks.

Why it matters

CVE-2026-73663 is a critical SQL injection vulnerability in FreePBX's missedcall module that requires immediate attention from FreePBX administrators and security teams to prevent potential database corruption, unauthorized remote access, and disruption to voice communication services.

• Potential database corruption and modification of FreePBX administrator accounts
• Unauthorized remote access to FreePBX systems
• Required verification of FreePBX version and patch level
• Potential disruption to voice communication services

Technical summary

The FreePBX missedcall module is vulnerable to SQL injection due to lack of escaping or bound parameters in the missedcalllog INSERT in agi-bin/missedcallnotify.php. An unauthenticated caller can inject SQL when a monitored extension goes unanswered, potentially corrupting the database and modifying FreePBX administrator accounts. This vulnerability requires immediate attention from FreePBX administrators and security teams to prevent potential database corruption and unauthorized remote access. The vulnerability can be mitigated by verifying FreePBX version and applying patches, reviewing FreePBX configuration, and monitoring for suspicious activity.

Defensive priority

High priority for FreePBX administrators and security teams to verify exposure and apply patches.

Recommended defensive actions

• Verify FreePBX version and apply patches to 16.0.11 or 17.0.4
• Review FreePBX configuration and monitor for suspicious activity
• Implement additional security measures to prevent SQL injection attacks
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but additional information on exploitation and impact is limited. Defenders should verify FreePBX version and patch level, review FreePBX configuration, and monitor for suspicious activity. The vulnerability is a critical SQL injection vulnerability in FreePBX's missedcall module that requires immediate attention from FreePBX administrators and security teams.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.