Skip to main content
CVE-2025-62173VulnerabilityPublished Updated

CVE-2025-62173: FreePBX restapps · SQL Injection

Affects FreePBX restappsSource CVE Database V5

0

Not known to be exploited · CVSS 8.6 High : upgrade to 16.0.41 soon.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Dec 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 2026-10-25.

What to do

Upgrade freepbx/restapps to 16.0.41.

Affected software

ProductAffectedFixed in
GitHubfreepbx/restappspkg:github/freepbx/restappsOther threatsAffected
  • <16.0.41
Fixed in
  • 16.0.41

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade FreePBX restapps to version 16.0.41 or later, or to versions above 17.0.6 once available, as these contain fixes for the vulnerability. 2. If immediate upgrade is not feasible, restrict access to the REST API endpoints by implementing network segmentation and firewall rules to limit access only to trusted administrators and management systems. 3. Enforce strong authentication and authorization controls to ensure only legitimate users with necessary privileges can access the REST API. 4. Implement input validation and sanitization at the application level where possible to prevent injection of malicious SQL commands. 5. Monitor logs for unusual or suspicious API activity that could indicate attempted exploitation. 6. Conduct regular security audits and penetration testing focused on telephony infrastructure to detect potential weaknesses. 7. Educate administrators on the risks of SQL injection and the importance of credential security to reduce insider threat risks. 8. Maintain up-to-date backups of telephony configuration and database to enable rapid recovery in case of compromise.

Description

## Summary Authenticated SQL Injection Vulnerability in Endpoint Module Rest API

References

Community reviews

Loading reviews…