OAuth2 authentication bypass via unconditional client validation
Published May 29, 2026 · Updated May 29, 2026
Authentication bypass in the FreePBX api module before 17.0.8 allows remote authenticated users to obtain OAuth2 access tokens. The validateClient() method in ClientRepository.php returns true unconditionally, so token issuance accepts any client_secret for a known client_id. A valid randomized client_id and at least one configured OAuth2 application are required; the default gql scope permits full GraphQL read and write access.
Summary
What happened
Authentication bypass in the FreePBX api module before 17.0.8 allows remote authenticated users to obtain OAuth2 access tokens. The validateClient() method in ClientRepository.php returns true unconditionally, so token issuance accepts any client_secret for a known client_id. A valid randomized client_id and at least one configured OAuth2 application are required; the default gql scope permits full GraphQL read and write access.
The record
- CVE
- CVE-2026-44237
- Published
- May 29, 2026
- Updated
- May 29, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1390, T1606
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 29, 2026CVE publishedPublication date reported by the CVE source.
- May 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo