CVE-2026-44237: CWE-1390: Weak Authentication in FreePBX security-reporting
FreePBX versions prior to 17.0.8 contain a vulnerability in the api module's OAuth2 implementation where client credentials are not properly validated during token issuance. Specifically, the validateClient() method in ClientRepository.php always returns true, allowing an attacker who knows a valid client_id to obtain OAuth2 access tokens without the correct client_secret. This weakness enables unauthorized access to the system's OAuth2 tokens. The issue is fixed in version 17.0.8.
AI Analysis
Technical Summary
CVE-2026-44237 affects FreePBX's security-reporting api module prior to version 17.0.8. The vulnerability arises because the validateClient() method in ClientRepository.php does not properly verify client credentials during OAuth2 token issuance, unconditionally returning true. This means that any actor with knowledge of a valid client_id can bypass the client_secret requirement and obtain OAuth2 access tokens, potentially leading to unauthorized access. The vulnerability is classified under CWE-1390 (Weak Authentication). The issue is resolved in FreePBX version 17.0.8.
Potential Impact
An attacker who knows a valid client_id can obtain OAuth2 access tokens without providing the correct client_secret, potentially allowing unauthorized access to FreePBX's API and associated resources. This could lead to unauthorized actions within the system that rely on OAuth2 authentication. There are no known exploits in the wild at this time.
Mitigation Recommendations
This vulnerability is fixed in FreePBX version 17.0.8. Users should upgrade to version 17.0.8 or later to remediate this issue. Patch status is not explicitly stated beyond this fix version, so confirm with the vendor advisory for the latest remediation guidance.
CVE-2026-44237: CWE-1390: Weak Authentication in FreePBX security-reporting
Description
FreePBX versions prior to 17.0.8 contain a vulnerability in the api module's OAuth2 implementation where client credentials are not properly validated during token issuance. Specifically, the validateClient() method in ClientRepository.php always returns true, allowing an attacker who knows a valid client_id to obtain OAuth2 access tokens without the correct client_secret. This weakness enables unauthorized access to the system's OAuth2 tokens. The issue is fixed in version 17.0.8.
CVSS v4.0
Score 7.6high
Affected software
pkg:github/freepbx/security-reportingRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-44237 affects FreePBX's security-reporting api module prior to version 17.0.8. The vulnerability arises because the validateClient() method in ClientRepository.php does not properly verify client credentials during OAuth2 token issuance, unconditionally returning true. This means that any actor with knowledge of a valid client_id can bypass the client_secret requirement and obtain OAuth2 access tokens, potentially leading to unauthorized access. The vulnerability is classified under CWE-1390 (Weak Authentication). The issue is resolved in FreePBX version 17.0.8.
Potential Impact
An attacker who knows a valid client_id can obtain OAuth2 access tokens without providing the correct client_secret, potentially allowing unauthorized access to FreePBX's API and associated resources. This could lead to unauthorized actions within the system that rely on OAuth2 authentication. There are no known exploits in the wild at this time.
Mitigation Recommendations
This vulnerability is fixed in FreePBX version 17.0.8. Users should upgrade to version 17.0.8 or later to remediate this issue. Patch status is not explicitly stated beyond this fix version, so confirm with the vendor advisory for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-05T15:42:40.519Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a199936e29bf47b50eaf3d2
Added to database: 05/29/2026, 13:48:38 UTC
Last enriched: 06/05/2026, 21:08:27 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 83
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.