CVE-2026-44237 FreePBX: Authenticated Access can lead to Subsequent OAuth2 Authentication Bypass in API Module
HighCVSS 7.6
EPSS 2.7%
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: total
- Technology
- PHP
Description
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.
Upgrade path
2 packages: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| Sangoma freepbx | < 17.0.8 | 17.0.8 | Fixed |
| FreePBX security-reporting | = < 17.0.8 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| FreePBX security-reporting | = < 17.0.8 | No fix listed |
| Sangoma freepbx | < 17.0.8 | 17.0.8 |
References
- https://github.com/FreePBX/security-reporting/security/advisories/GHSA-vgjf-4h63-8vcc mitigation vendor-advisory