dbcve.org
FreepbxApplication · Sangoma

CVE-2026-44237

HIGH · 8.1 CVSS v3.1 Published 2026-05-29
Fix available
A fix is available. Upgrade to 17.0.8 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The OAuth2 validateClient() method in FreePBX's ClientRepository.php fails to verify the client_secret, unconditionally returning true for any request with a valid client_id. This allows attackers to obtain OAuth2 access tokens without authenticating with the correct client secret.

MitigationUpgrade FreePBX to version 17.0.8 or later. Until then, restrict network access to OAuth2 endpoints and monitor for unauthorized token issuance.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FreepbxApplication
Affected:< 17.0.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check FreePBX version
    Run 'fwconsole ma list' or check the FreePBX admin dashboard System Admin > System Status for the installed version number
    Affected if The installed version is lower than 17.0.8 (e.g., 17.0.7, 16.0, 15.0, etc.)
  2. Verify api module is installed
    Run 'fwconsole ma list | grep api' or check Admin > Module Admin to confirm the api module is installed
    Affected if The api module is present on the system
  3. Confirm OAuth2 is configured
    Check for OAuth2 client configurations in /var/www/html/admin/modules/api/ directory, or look for OAuth client records in the FreePBX database (fwconsole dbquery)
    Affected if OAuth2 clients are defined in the api module configuration
  4. Inspect validateClient method
    Examine the file /var/www/html/admin/modules/api/Repo/ClientRepository.php and locate the validateClient() method - check if it returns true after checking only client_id without validating client_secret
    Affected if The validateClient() method returns true without fully validating both client_id and client_secret

A user is affected if they are running FreePBX version below 17.0.8 with the api module installed and OAuth2 clients configured, where the validateClient() method only checks client_id.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 17.0.8 or later
Fixed in 17.0.8
Interim mitigation

Upgrade FreePBX to version 17.0.8 or later. Until then, restrict network access to OAuth2 endpoints and monitor for unauthorized token issuance.

Recommended fix High confidence

17.0.8

  1. 1. Back up the FreePBX system before performing any upgrade
  2. 2. Upgrade FreePBX to version 17.0.8 or later
  3. 3. Verify the upgrade was successful by checking the version
  4. 4. Test the OAuth2 functionality to confirm the client credential validation is now working correctly
  5. 5. Ensure that client_secret is now properly required for token issuance
Caveat Review the FreePBX 17.0.8 release notes for any breaking changes or migration considerations before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Freepbx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44237 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44237 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data