dbcve.org
FreepbxApplication · Sangoma

CVE-2026-28209

HIGH · 7.2 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 →
78/100
Remediation priority · High
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, 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.

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

A command injection vulnerability exists in FreePBX's recordings module when using the ElevenLabs Text-to-Speech engine. User-supplied input in the TTS configuration or text parameters is not properly sanitized before being passed to system commands, allowing an authenticated attacker to execute arbitrary commands on the underlying operating system.

MitigationUpgrade FreePBX to version 16.0.20 or 17.0.5 or later. If immediate patching is not possible, disable the ElevenLabs TTS feature in the recordings module and review any exposed interfaces for untrusted input.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 version
    Run `fwconsole ma list | grep -i core` or check /etc/sangoma/freepbx.conf for the version string
    Affected if Version is between 16.0.17.2 and 16.0.19.x, or between 17.0.2.4 and 17.0.4.x
  2. Verify recordings module is installed
    Run `fwconsole ma list | grep -i recordings` to confirm the recordings module is present
    Affected if Recordings module is installed and vulnerable version of FreePBX is in range
  3. Check ElevenLabs TTS configuration
    Inspect the FreePBX database: `mysql -e "use asterisk; SELECT * FROM recordings_tts WHERE engine='elevenlabs';"` or check /var/www/html/admin/modules/recordings/*.php for elevenlabs settings
    Affected if ElevenLabs TTS engine is configured or enabled in the recordings module settings
  4. Look for ElevenLabs API credentials
    Check /etc/freepbx.conf or the asterisk database for elevenlabs API keys: `mysql -e "use asterisk; SELECT * FROM kvstore WHERE module LIKE '%eleven%' OR `key` LIKE '%eleven%';"`
    Affected if API keys for ElevenLabs are present in the FreePBX configuration

A user is affected if their FreePBX version falls within 16.0.17.2-16.0.19.x or 17.0.2.4-17.0.4.x AND the recordings module with ElevenLabs TTS is 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. If immediate patching is not possible, disable the ElevenLabs TTS feature in the recordings module and review any exposed interfaces for untrusted input.

Recommended fix High confidence

FreePBX 16.0.20 (for 16.x branch) or FreePBX 17.0.5 (for 17.x branch)

  1. Backup the FreePBX system including all configurations, recordings, and databases before proceeding with any upgrade
  2. Identify the current FreePBX version by running 'fwconsole ma list' or checking the admin GUI dashboard
  3. For FreePBX 16.x versions (>= 16.0.17.2): Upgrade to version 16.0.20 by running the system update commands (e.g., 'fwconsole ma upgradeall' or through the Admin > Module Admin > Check Online interface)
  4. For FreePBX 17.x versions (>= 17.0.2.4): Upgrade to version 17.0.5 using the same update mechanism
  5. After upgrade completion, clear all caches with 'fwconsole cacheclear' or equivalent
  6. Verify the ElevenLabs TTS functionality works correctly in the Recordings module with the new version
  7. Confirm the FreePBX version now shows 16.0.20 or 17.0.5 respectively

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

Fix this in Freepbx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28209 — 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-28209 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