dbcve.org
FreepbxApplication · Sangoma

CVE-2026-28210

HIGH · 8.8 CVSS v3.1 Published 2026-03-05
Fix available
A fix is available. Upgrade to 16.0.49 / 17.0.7 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. Prior to versions 16.0.49 and 17.0.7, FreePBX module cdr (Call Data Record) is vulnerable to SQL query injection. This issue has been patched in versions 16.0.49 and 17.0.7.

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

The FreePBX cdr (Call Data Record) module is vulnerable to SQL query injection due to insufficient input sanitization. An attacker could exploit this by injecting malicious SQL statements through user-supplied input processed by the cdr module, potentially allowing unauthorized data access, data manipulation, or in some database configurations, remote code execution.

MitigationUpgrade FreePBX to version 16.0.49 or 17.0.7 to apply the patch for the SQL injection vulnerability in the cdr module. Until patched, consider restricting network access to the FreePBX administrative interface and monitoring database logs for suspicious SQL patterns.

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, < 16.0.49>= 17.0, < 17.0.7

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 version
    Log into the FreePBX administrative interface and navigate to Admin > System Admin > Version, or run 'fwconsole ma list' or 'grep -i version /etc/sangoma-release' from command line
    Affected if The installed version is 16.0.x before 16.0.49, or 17.0.x before 17.0.7
  2. Verify CDR module is installed
    Run 'fwconsole ma list | grep cdr' or check via Admin > Module Admin to confirm the cdr module is installed
    Affected if The cdr module is present on the system
  3. Confirm CDR module is enabled
    Check if the cdr module is loaded and active - run 'fwconsole ma list | grep -i cdr' and look for status 'Enabled' or 'Running'
    Affected if The cdr module is enabled and processing calls
  4. Check for CDR-related web access
    Review web server access logs for requests to CDR-related endpoints (typically /admin/config.php?type=setup&display=cdr or similar CDR routes) with unusual SQL-like patterns
    Affected if CDR module web interface is accessible and processing user-supplied input

The environment is affected if FreePBX version is 16.0.0-16.0.48 or 17.0.0-17.0.6 AND the cdr module is 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.49 / 17.0.7 or later
Fixed in 16.0.4917.0.7
Interim mitigation

Upgrade FreePBX to version 16.0.49 or 17.0.7 to apply the patch for the SQL injection vulnerability in the cdr module. Until patched, consider restricting network access to the FreePBX administrative interface and monitoring database logs for suspicious SQL patterns.

Recommended fix High confidence

FreePBX 16.0.49 or FreePBX 17.0.7 (depending on your major version branch)

  1. Backup your FreePBX system including all configurations and CDR data
  2. Identify your current FreePBX version using the admin GUI or command line (fwconsole ma list)
  3. For FreePBX 16.x systems: Update to version 16.0.49 or later via: fwconsole ma upgradeall or through the Module Admin interface
  4. For FreePBX 17.x systems: Update to version 17.0.7 or later via: fwconsole ma upgradeall or through the Module Admin interface
  5. After upgrade, restart FreePBX services: fwconsole restart
  6. Verify the CDR module version reflects the patched release (16.0.49 or 17.0.7)
Caveat Standard FreePBX upgrade precautions apply - test in non-production 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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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