CVE-2026-54708: FreePBX security-reporting · Path Traversal
Affects FreePBX security-reportingSource CVE Database V5
Not known to be exploited · CVSS 8.6 High : upgrade to 17.0.7 or 16.0.72 soon.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 17.0.7, 16.0.72
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Sep 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 13 Nov 2026.
What to do
Upgrade security-reporting and freepbx/security-reporting to 17.0.7 or 16.0.72.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FreePBXsecurity-reporting | Affected
| Fixed in
|
| FreePBXsecurity-reporting | Affected
| Fixed in
|
GitHubfreepbx/security-reportingpkg:github/freepbx/security-reportingOther 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
Upgrade FreePBX to version 16.0.72 or later, or 17.0.7 or later, where this vulnerability is patched. No other mitigations are indicated by the vendor advisory.
Description
FreePBX is an open source IP PBX. Prior to versions 16.0.72 and 17.0.7, a critical vulnerability exists in the FreePBX backup Module that allows authenticated attackers to execute arbitrary code on the server. Authentication with a known username that has sufficient access permissions and/or write access to backup files is required. This vulnerability is caused by improper path sanitization in the backup restore functionality, enabling attackers to upload malicious PHP files to the web root directory. This issue has been patched in versions 16.0.72 and 17.0.7.