Is CVE-2026-44237 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44237 being exploited in the wild.

How severe is CVE-2026-44237?

Informational severity, with a CVSS score of 7.6, published 29 May 2026.

Is there a fix for CVE-2026-44237?

A patch was published on 2026-05-29: Fix released in version 17.0.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44237 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-44237?

Check whether you run FreePBX Api Module at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44237: FreePBX api module OAuth2 authentication bypass

CVE-2026-44237 · Severity: info · CVSS 7.6 · Published 2026-05-29

FreePBX is an open-source phone system (IP PBX) used by businesses for managing telecommunications. A security flaw in its API module allows an attacker who has obtained a specific internal ID (client_id) to bypass authentication and gain full administrative access to the system's data and settings. This could lead to unauthorized access to call records, configuration changes, or complete control over the phone system's operations.

Vendors: FreePBX.

Quick answers

Is CVE-2026-44237 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44237 being exploited in the wild.
How severe is CVE-2026-44237?: Informational severity, with a CVSS score of 7.6, published 29 May 2026.
Which products and versions are affected?: FreePBX Api Module < 17.0.8.
Is there a fix for CVE-2026-44237?: A patch was published on 2026-05-29: Fix released in version 17.0.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44237 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44237?: Check whether you run FreePBX Api Module at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The FreePBX api module (version 17) contains an authentication bypass in its OAuth2 implementation. The `validateClient()` method in `ClientRepository.php` was found to unconditionally return `true`, effectively ignoring the `client_secret` during the `client_credentials` grant flow. An attacker who knows or has obtained a valid `client_id` (typically a 64-character string found in the admin panel or backups) can request OAuth2 access tokens without the corresponding secret. These tokens grant the default `gql` scope, providing full read/write access to all GraphQL mutations and queries. The vulnerability was introduced during the PHP version upgrade for FreePBX v17 and is fixed in version 17.0.8.

Affected products

FreePBX FreePBX api module < 17.0.8

Timeline

2026-05-11: advisory: GitHub advisory published by maintainer
2026-05-29: disclosed: CVE published to NVD
2026-05-29: patched: Fix released in version 17.0.8

References

https://github.com/FreePBX/security-reporting/security/advisories/GHSA-vgjf-4h63-8vcc

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.