Skip to main content
VulnerabilityPublished Updated

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

Affects FreePBX security-reportingSource CVE Database V5

0
Compare

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

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
8.5% chance of exploitation in 30 days – higher than 95% 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:N/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 29 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 versions 16.0.20 or 17.0.5 or later, where the vulnerability is patched.
  2. Restrict administrative access to the FreePBX interface using network segmentation, VPNs, and strict firewall rules to limit exposure to trusted IP addresses only.
  3. Enforce strong authentication and authorization controls to prevent privilege escalation that could enable exploitation.
  4. Regularly audit user accounts and permissions to ensure only necessary high-privilege access is granted.
  5. Monitor system and application logs for unusual command execution or access patterns indicative of exploitation attempts.
  6. Implement intrusion detection/prevention systems (IDS/IPS) tuned to detect suspicious activity related to FreePBX.
  7. Consider deploying application-layer firewalls or web application firewalls (WAF) to filter malicious input targeting the recordings module.
  8. Educate administrators on the risks of OS command injection and the importance of timely patching.
  9. If immediate patching is not feasible, disable or restrict access to the recordings module temporarily as a stopgap measure.
  10. Maintain regular backups of PBX configurations and recordings to enable 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, multiple command injection vulnerabilities exist in the recordings module. This issue has been patched in versions 16.0.20 and 17.0.5.

References

Community reviews

Loading reviews…