Vulnerability in Freepbx Security-Reporting
CVE-2026-44237
FreePBX is an open source IP PBX. Prior to 17.0.8, the FreePBX api module's OAuth2 implementation does not sufficiently validate client credentials during token issuance. Knowledge of a valid client_id is required. The validateClient() method in ClientRepository.php unconditionally returns true, allowing any party with knowledge of a valid client_id to obtain OAuth2 access tokens without providing the correct client_secret. This vulnerability is fixed in 17.0.8.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.
EPSS exploit prediction
EPSS: 0.004 (27.0th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 27th percentile — 27.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.002 · newest: 0.004 · change: +0.001
Affected products
- Freepbx Security-Reporting — versions < 17.0.8
- Sangoma Freepbx
Weakness classification (CWE)
References
- github.com/FreePBX/security-reporting/security/advisories/GHSA-vgjf-4h63-8vcc (Mitigation, Vendor Advisory)
Frequently asked questions
- What is CVE-2026-44237?
- CVE-2026-44237 is a high-severity vulnerability in Freepbx Security-Reporting, classified under Weak Authentication. CVSS score: 8.1/10. Published 2026-05-29.
- How severe is CVE-2026-44237?
- High severity. CVSS v3 base score is 8.1 out of 10.