Skip to main content
VulnerabilityPublished Updated

CVE-2026-28209: FreePBX security-reporting · OS Command Injection

Affects FreePBX security-reportingSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 17.0.5 or 16.0.20 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 17.0.5, 16.0.20
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade security-reporting and freepbx/security-reporting to 17.0.5 or 16.0.20.

Affected software

ProductAffectedFixed in
FreePBXsecurity-reportingAffected
  • >=17.0.2.4 <17.0.5
Fixed in
  • 17.0.5
FreePBXsecurity-reportingAffected
  • >=16.0.17.2 <16.0.20
Fixed in
  • 16.0.20
GitHubfreepbx/security-reportingpkg:github/freepbx/security-reportingOther threatsAffected
  • >=16.0.17.2 <16.0.20
  • >=17.0.2.4 <17.0.5
Fixed in
  • 16.0.20
  • 17.0.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately upgrade FreePBX installations to version 16.0.20 or 17.0.5 or later to apply the official patches addressing this vulnerability.
  2. Restrict access to the FreePBX administrative interface to trusted networks and enforce strong authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise.
  3. Monitor system logs and command execution traces for unusual activity indicative of command injection attempts or unauthorized access.
  4. Implement network segmentation to isolate telephony infrastructure from general user networks, limiting lateral movement if compromise occurs.
  5. Regularly audit user privileges and remove unnecessary high-level access to minimize the number of users who can exploit this vulnerability.
  6. Consider deploying application-layer firewalls or intrusion detection/prevention systems capable of detecting command injection patterns targeting FreePBX.
  7. Maintain up-to-date backups of configuration and call data to enable rapid recovery in case of compromise.

Description

FreePBX is an open source IP PBX. From versions 16.0.17.2 to before 16.0.20 and from version 17.0.2.4 to before 17.0.5, a command injection vulnerability exists in FreePBX when using the ElevenLabs Text-to-Speech (TTS) engine in the recordings module. This issue has been patched in versions 16.0.20 and 17.0.5.

References

Community reviews

Loading reviews…