dbcve.org
FreepbxApplication · Sangoma

CVE-2026-28287

HIGH · 8.8 CVSS v3.1 Published 2026-03-05
Fix available
A fix is available. Upgrade to 16.0.20 / 17.0.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple command injection vulnerabilities exist in FreePBX's recordings module, allowing attackers to execute arbitrary system commands through unsanitized user input. The CVSS 8.8 score indicates high exploitability, likely requiring some level of authentication but providing significant impact on system compromise.

MitigationUpgrade FreePBX to version 16.0.20 or 17.0.5 (or later) to patch the command injection vulnerabilities in the recordings module.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FreepbxApplication
Affected:>= 16.0.17.2, < 16.0.20>= 17.0.2.4, < 17.0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify FreePBX installation
    Check if FreePBX is installed on the system by looking for common FreePBX directories such as /var/www/html/freepbx or by running 'freepbx -V' if the CLI tool is available
    Affected if FreePBX is not installed on the system
  2. Determine FreePBX version
    Access the FreePBX admin GUI and navigate to Admin > System Admin > Version, or check the file /etc/freepbx.conf for the version string, or run 'fwconsole ma list | grep -i system' to see version info
    Affected if The installed version falls within 16.0.17.2 to 16.0.19.x OR 17.0.2.4 to 17.0.4.x
  3. Verify recordings module is loaded
    Run 'fwconsole ma list | grep -i recording' or access the GUI Modules page to confirm the recordings module is installed and enabled
    Affected if The recordings module is installed and enabled on an affected FreePBX version
  4. Confirm vulnerability applicability
    The command injection vulnerability exists specifically in the recordings module. Check module version with 'fwconsole ma info recordings'
    Affected if The recordings module is active on FreePBX versions 16.0.17.2 through 16.0.19.x or 17.0.2.4 through 17.0.4.x

A system is affected if it runs FreePBX version 16.0.17.2 through 16.0.19.x or 17.0.2.4 through 17.0.4.x with the recordings module installed and enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 16.0.20 / 17.0.5 or later
Fixed in 16.0.2017.0.5
Interim mitigation

Upgrade FreePBX to version 16.0.20 or 17.0.5 (or later) to patch the command injection vulnerabilities in the recordings module.

Recommended fix High confidence

FreePBX 16.x users: upgrade to 16.0.20; FreePBX 17.x users: upgrade to 17.0.5

  1. Identify the currently installed FreePBX version by running 'fwconsole ma list' or checking the FreePBX admin dashboard
  2. If running FreePBX 16.x (versions 16.0.17.2 through 16.0.19.x), plan upgrade to version 16.0.20
  3. If running FreePBX 17.x (versions 17.0.2.4 through 17.0.4.x), plan upgrade to version 17.0.5
  4. Backup the FreePBX system and all recordings before performing the upgrade
  5. Run the module update via 'fwconsole ma update recordings' or use the FreePBX Admin GUI > Modules > Check Online > Update All
  6. Alternatively, download and install the recordings module directly from the FreePBX repository for version 16.0.20 or 17.0.5
  7. After upgrade, verify the recordings module version shows 16.0.20 or 17.0.5
  8. Test recordings module functionality to confirm the fix works correctly
Caveat Review FreePBX release notes for 16.0.20 and 17.0.5 for any module dependencies or configuration changes that may affect other components

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Freepbx Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28287 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28287 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data