CVE-2026-44238
SQLi in FreePBX CDR Reports via POST order/sort parameters.
Is CVE-2026-44238 being exploited?
Not confirmed. CVE-2026-44238 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-44238?
CVE-2026-44238 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-44238?
Yes. A fix has been recorded for CVE-2026-44238. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-44238 affect?
CVE-2026-44238 affects FreePBX CDR Reports module (pre-16.0.50, pre-17.0.11). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-44238?
Upgrade to FreePBX 16.0.50 or 17.0.11+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker with CDR access can inject via POST to read/modify CDR data.
Immediate action required
- affected< 16.0.50
- affected>= 17.0.1 and < 17.0.11
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.