CVE Tools

CVE-2026-44237

FreePBX: Authenticated Access can lead to Subsequent OAuth2 Authentication Bypass in API Module

Published: May 29, 2026Updated: Jun 1, 2026 Sources: CVE List NVDCWE-1390

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.

CVSS Vector Breakdown

AV:NAC:LPR:LUI:NS:UC:HI:HA:N
Exploitability
AV:NAttack Vector
Network
AC:LAttack Complexity
Low
PR:LPrivileges Required
Low
UI:NUser Interaction
None
Scope
S:UScope
Unchanged
Impact
C:HConfidentiality
High
I:HIntegrity
High
A:NAvailability
None

Weaknesses

Affected Products

freepbxoss-projectCommunicationsaka freepbx, security-reporting, endpoint
sangomacommercialCACommunicationsaka freepbx, certified asterisk, asterisk

Exploitability

Workaround Available

References

Timeline

Published
May 29, 2026
Last Updated
Jun 1, 2026

Unlock Complete Vulnerability Intelligence

Get the full picture for CVE-2026-44237 and every CVE in our database. Create a free account — no credit card required.

Create Free Account
Plain-language analysis
Impact assessment and exploitation scenario in plain English
Attack graph visualization
Interactive attack path and kill chain mapping
Exploit details & PoC links
ExploitDB, Metasploit, GitHub PoCs with direct links
Nuclei scanner templates
Ready-to-use vulnerability scanner templates
Full remediation guide
Patch instructions, workarounds, and compliance impact
Interactive AI chat
Ask questions about this vulnerability in natural language
Related vulnerabilities
Semantically similar CVEs and attack patterns
REST API & MCP access
Integrate vulnerability data into your workflows