CVE-2026-73660: FreePBX tts · OS Command Injection
Affects FreePBX ttsSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 17.0.5.4 or 16.0.6 soon.
Data as of 10 Nov 2026, 23:24 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 17.0.5.4, 16.0.6
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/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: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade tts and freepbx/tts to 17.0.5.4 or 16.0.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FreePBXtts | Affected
| Fixed in
|
| FreePBXtts | Affected
| Fixed in
|
GitHubfreepbx/ttspkg:github/freepbx/ttsOther 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 versions 16.0.6 and 17.0.5.4. Users should upgrade to these versions or later to remediate the issue. No other mitigation or workaround is indicated in the available data.
Description
FreePBX is an open source IP PBX. Prior to 16.0.6 and 17.0.5.4, the FreePBX Text-To-Speech module allows an authenticated administrator to save a TTS destination name that is HTML-encoded for storage, decoded during dialplan generation, passed as an AGI argument, and used to build filenames inside agi-bin/propolys-tts.agi. The TTS destination name reaches a raw shell-command execution path, allowing arbitrary operating-system command execution as the asterisk service user. This issue is fixed in versions 16.0.6 and 17.0.5.4.