Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

Quick assessment

Affected
FreePBX missedcall
Exploitation
Public or AI PoC available; prioritize validation
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

FreePBX missedcall是FreePBX团队的一个未接来电提醒模块。 FreePBX missedcall 16.0.11之前版本和17.0.1至17.0.4之前版本存在SQL注入漏洞,该漏洞源于未对精心构造的SIP From标头中的调用者ID名称进行转义或绑定参数,可能导致未经身份验证的攻击者在受监控分机无人应答时注入SQL,破坏数据库并修改FreePBX管理员账户以获取未经授权的远程访问。

CVSS 9.3 · Critical EPSS 1.66% · P76

Affected Version Matrix 2

VendorProduct Version RangeStatus
FreePBX missedcall < 16.0.11 affected
>= 17.0.1, < 17.0.4 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-73663

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
FreePBX: Unauthenticated SQL injection in FreePBX missedcall via inbound Caller ID name leads to administrator takeover
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
SQL命令中使用的特殊元素转义处理不恰当(SQL注入)
Source: CVE Program / CVE List V5
Vulnerability Title
FreePBX missedcall SQL注入漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
FreePBX missedcall是FreePBX团队的一个未接来电提醒模块。 FreePBX missedcall 16.0.11之前版本和17.0.1至17.0.4之前版本存在SQL注入漏洞,该漏洞源于未对精心构造的SIP From标头中的调用者ID名称进行转义或绑定参数,可能导致未经身份验证的攻击者在受监控分机无人应答时注入SQL,破坏数据库并修改FreePBX管理员账户以获取未经授权的远程访问。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
FreePBX missedcall < 16.0.11 -

II. Public POCs for CVE-2026-73663

# POC Description Source Link Shenlong Link
AI-Generated POC Verified env Premium
Qwen3.6-35B-A3B · 11787 chars
Pro+ exclusive includes:
Vulnerability reproduction recording (real sandbox build + trigger, exclusive)
In-depth vulnerability mechanism
Trigger conditions & impact
Full executable POC code
Exploit chain & mitigation
POC zip download
100+ AI POC generations per month

III. Intelligence Information for CVE-2026-73663

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-73663 (2)

Vendor Advisories for CVE-2026-73663 (1)

Same Patch Batch · FreePBX · 2026-08-13 · 6 CVEs total

CVE-2026-73665 9.3 CRITICAL FreePBX UCP: Unauthenticated remote code execution via socket.io namespace auth bypass and
CVE-2026-73661 8.6 HIGH FreePBX: Authenticated Framework AUTHTYPE Can Be Restored From a Crafted Backup
CVE-2026-73664 8.6 HIGH FreePBX: Authenticated Arbitrary SSH Key Injection via Backup Module
CVE-2026-73662 7.6 HIGH Authenticated FreePBX Music RCE via mpg123 and Asterisk Call Files
CVE-2026-73660 7.5 HIGH FreePBX: Authenticated TTS AGI Command Injection Through TTS Name

IV. Related Vulnerabilities

V. Comments for CVE-2026-73663

No comments yet


Leave a comment