dbcve.org
FreepbxApplication · Sangoma

CVE-2025-55211

HIGH · 8.8 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 17.0.21 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 web-based graphical user interface. From 17.0.19.11 to before 17.0.21, authenticated users of the Administrator Control Panel (ACP) can run arbitrary shell commands by maliciously changing languages of the framework module. This vulnerability is fixed in 17.0.21.

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

FreePBX versions 17.0.19.11 through 17.0.20.x contain a command injection vulnerability in the Administrator Control Panel (ACP). Authenticated administrators can execute arbitrary shell commands by manipulating language settings in the framework module, likely through unsanitized input being passed to a system call.

MitigationUpgrade FreePBX to version 17.0.21 or later. Limit ACP access to trusted administrators only, and review admin accounts for unauthorized changes.

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:>= 17.0.19.11, < 17.0.21

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. Check FreePBX version
    Log into the Administrator Control Panel (ACP) and navigate to Admin > System Admin > Version Info, or run 'fwconsole ma list' from command line to see installed modules and version
    Affected if Installed version is 17.0.19.11 through 17.0.20.x (any version >= 17.0.19.11 but < 17.0.21)
  2. Verify ACP access is enabled
    Check if the Administrator Control Panel web interface is exposed and accessible by attempting to reach the login page at your FreePBX host URL
    Affected if ACP is accessible over the network to untrusted users
  3. Identify administrator accounts
    Navigate to Admin > Administrators in the ACP to list all configured admin accounts, or query the database table 'freepbx_users' or 'ampusers'
    Affected if Multiple admin accounts exist beyond the initial setup account, or unknown admin accounts are present
  4. Review framework module language settings
    In ACP, go to Settings > Advanced Settings > Language and inspect the current language configuration for the framework module
    Affected if Language settings can be modified and are not sanitized before use in system calls

You are affected if FreePBX version is 17.0.19.11 through 17.0.20.x and the ACP is accessible to untrusted administrators who can modify language settings in the framework module.

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 17.0.21 or later
Fixed in 17.0.21
Interim mitigation

Upgrade FreePBX to version 17.0.21 or later. Limit ACP access to trusted administrators only, and review admin accounts for unauthorized changes.

Recommended fix High confidence

FreePBX 17.0.21

  1. 1. Create a complete backup of the current FreePBX system including all configurations, extensions, and recordings
  2. 2. Access the FreePBX Administrator Control Panel (ACP)
  3. 3. Navigate to the Admin module or System Administration section
  4. 4. Check for updates or navigate to the module administration interface
  5. 5. Upgrade the FreePBX framework to version 17.0.21 or later
  6. 6. After upgrade, clear any cached data and restart the FreePBX services (fwconsole restart)
  7. 7. Verify the upgrade was successful by checking the FreePBX version
  8. 8. Test that the language settings in the framework module work correctly without command injection
Caveat Minor version upgrades typically have minimal breaking changes, but always test in a staging environment first

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

Fix this in Freepbx Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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