Skip to main content
VulnerabilityPublished Updated

CVE-2025-55739: FreePBX api · Use of Hard-coded Credentials

Affects FreePBX apiSource CVE Database V5

0

Not known to be exploited · CVSS 5.1 Medium : upgrade to 15.0.13 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 15.0.13
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade FreePBX api to 15.0.13.

Affected software

ProductAffectedFixed in
FreePBX apiAffected
  • <15.0.13
Fixed in
  • 15.0.13

AI-suggested

European organizations should immediately verify their FreePBX versions and upgrade to 15.0.13, 16.0.15, or 17.0.3 or later to apply the patch that eliminates the hard-coded OAuth key. If immediate patching is not feasible, administrators should disable the 'api' module or restrict its remote access using network-level controls such as firewalls or VPNs to limit exposure. Audit existing API keys and JWT tokens for signs of unauthorized use. Implement strict monitoring and logging of API access to detect anomalous activity. Additionally, enforce strong administrative access controls and multi-factor authentication for PBX management interfaces. Network segmentation should isolate PBX systems from general user networks to reduce attack surface. Regularly review and update security policies related to telephony infrastructure. Finally, coordinate with vendors and security teams to stay informed about any emerging exploits or indicators of compromise related to this vulnerability.

Description

api is a module for FreePBX@, which is an open source GUI that controls and manages Asterisk© (PBX). In versions lower than 15.0.13, 16.0.2 through 16.0.14, 17.0.1 and 17.0.2, there is an identical OAuth private key used across multiple systems that installed the same FreePBX RPM or DEB package. An attacker with access to the shared OAuth private key could forge JWT tokens, bypass authentication, and potentially gain full access to both REST and GraphQL APIs. Systems with the "api" module enabled, configured and previously activated by an administrator for remote inbound connections may be affected. This issue is fixed in versions 15.0.13, 16.0.15 and 17.0.3.

References

Community reviews

Loading reviews…