CVE-2026-44238
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 · uneditedFreePBX is an open source IP PBX. Prior to 16.0.50 and 17.0.11, the CDR Reports module page allows SQL injection through the order and sort POST parameters. Authentication with a FreePBX Administration Control Panel account that has CDR section access is required. Full administrator privileges are not needed. This vulnerability is fixed in 16.0.50 and 17.0.11.
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 confidenceThe CDR Reports module in FreePBX IP PBX contains a SQL injection vulnerability in the 'order' and 'sort' POST parameters. An attacker with a valid FreePBX Administration Control Panel account that has CDR section access (but not full administrator privileges) can inject malicious SQL queries. The vulnerability affects versions prior to 16.0.50 and 17.0.11.
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< 16.0.50>= 17.0, < 17.0.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify FreePBX installation and versionRun 'fwconsole ma list' or check /etc/freepbx.conf for the version string. Alternatively, access the admin web interface and check the System Administration or Dashboard page for the FreePBX version.Affected if The installed version is less than 16.0.50, or greater than or equal to 17.0 but less than 17.0.11
-
Verify CDR module is installed and enabledRun 'fwconsole ma list | grep cdr' or check the Modules Admin page in the web interface for the CDR Reports module.Affected if The CDR Reports module is installed and enabled
-
Check for users with CDR section accessReview user permissions in the web interface under Admin > Users or User Management. Look for users assigned to the CDR section or reports functionality.Affected if Any user account exists with CDR section or report access (not just full administrators)
-
Inspect CDR Reports endpoint for vulnerable parametersExamine the HTTP requests made when accessing the CDR Reports page. Look for POST parameters named 'order' and 'sort' being sent to the CDR reporting interface.Affected if The CDR Reports module accepts 'order' and 'sort' as POST parameters without sanitization (this would require code review or testing in a non-production environment)
A defender is affected if their FreePBX version is below 16.0.50 or between 17.0.0 and 17.0.10 inclusive, AND the CDR Reports module is installed with at least one user having CDR section access.
Generated from the published advisory. Verify against your own configuration.
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 · scoped16.0.5017.0.11
Upgrade FreePBX to version 16.0.50 or 17.0.11 or later to patch the SQL injection vulnerability. Limit CDR section access to only necessary personnel until the upgrade is applied.
Upgrade to FreePBX 16.0.50 (if on 16.x branch) or FreePBX 17.0.11 (if on 17.x branch)
- 1. Back up your FreePBX system before proceeding with any upgrade.
- 2. Determine your current FreePBX version by logging into the Administration Control Panel.
- 3. If running FreePBX 16.x (version < 16.0.50), upgrade to version 16.0.50.
- 4. If running FreePBX 17.x (version >= 17.0 and < 17.0.11), upgrade to version 17.0.11.
- 5. Use the FreePBX module admin or standard upgrade procedures to apply the update.
- 6. After upgrade, verify the CDR Reports module is functioning correctly and that the vulnerability is remediated.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44238 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44238 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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