Exploit Against FreePBX (CVE-2025-57819) with code execution., (Tue, Oct 7th)
Source SANS ISC Handlers Diary
Exploited in the wild · KEV due 19 Sep 2025 · public exploit available (Metasploit, Exploit-DB) · fixed in 17.0.3 : patch endpoint now.
Data as of 5 Nov 2026, 00:01 UTC
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
- Patch
- Available – fixed in 17.0.3, 16.0.89, 15.0.66
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 28 Aug 2025
Detectable: evidence found.
Weaponized: evidence found.
1 Metasploit module · 1 Exploit-DB entry, 1 year after disclosure
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 1 day after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by GitHub, Inc.
, 8 days before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 3 minutes after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
, 1 day after disclosure
KEV remediation due
US federal deadline
, 22 days after disclosure
First Exploit-DB entry (opens in a new tab)
FreePBX 17.0.2 - Remote Code Execution (RCE)
, 1 year after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade endpoint to 17.0.3, 16.0.89 or 15.0.66.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FreePBXendpoint | Affected
| Fixed in
|
| FreePBXendpoint | Affected
| Fixed in
|
| FreePBXendpoint | Affected
| Fixed in
|
AI-suggested
European organizations should immediately audit their FreePBX installations for signs of compromise, focusing on the 'cron_jobs' database table for unauthorized entries. Implement network segmentation to isolate PBX systems from broader corporate networks to limit lateral movement. Restrict administrative interface access using VPNs, IP whitelisting, or multi-factor authentication to reduce exposure. Monitor web server logs and cron job executions for unusual activity, including unexpected PHP files or recurring cron jobs. If patches are not yet released, consider temporarily disabling or restricting access to the vulnerable admin modules. Employ web application firewalls (WAFs) with rules to detect and block SQL injection attempts targeting the FreePBX interface. Regularly back up PBX configurations and databases to enable recovery from compromise. Finally, conduct user awareness training to recognize signs of PBX misuse and implement incident response plans specific to telephony infrastructure.
Description
FreePBX is a popular PBX system built around the open source VoIP system Asterisk. To manage Asterisk more easily, it provides a capable web-based admin interface. Sadly, like so many web applications, it has had its share of vulnerabilities in the past. Most recently, a SQL injection vulnerability was found that allows attackers to modify the database.