Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-67513: CWE-521: Weak Password Requirements in FreePBX endpoint

0
Medium
VulnerabilityCVE-2025-67513cvecve-2025-67513cwe-521
Published: Wed Dec 10 2025 (12/10/2025, 22:43:06 UTC)
Source: CVE Database V5
Vendor/Project: FreePBX
Product: endpoint

Description

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/14/2026, 07:12:25 UTC

Technical Analysis

CVE-2025-67513 identifies a weakness in the FreePBX Endpoint Manager module, which is widely used to manage telephony endpoints in FreePBX systems. The vulnerability stems from the default configuration of the app_password parameter, which is set to a 6-digit numeric password. Such a password space (1 million possibilities) is susceptible to brute force attacks, especially since no authentication or user interaction is required to attempt guesses. The app_password controls access to critical telephony components including extensions, voicemail, user manager, DPMA, or EPM phone admin passwords depending on local configuration, thereby potentially granting an attacker unauthorized administrative control over telephony endpoints. The affected versions are all releases prior to 16.0.96 and versions from 17.0.1 up to but not including 17.0.10. The vulnerability has a CVSS 4.0 base score of 6.9, reflecting its network attack vector, low attack complexity, and no required privileges or user interaction. Although no known exploits are currently reported in the wild, the ease of brute forcing weak numeric passwords makes this a significant risk. The issue was addressed by FreePBX in versions 16.0.96 and 17.0.10 by presumably enforcing stronger default passwords or allowing administrators to set more secure credentials.

Potential Impact

For European organizations, exploitation of this vulnerability could lead to unauthorized access to telephony systems, allowing attackers to intercept calls, manipulate voicemail, or disrupt telephony services. This could result in confidentiality breaches of sensitive communications, integrity violations through unauthorized configuration changes, and availability impacts if telephony endpoints are disabled or misconfigured. Organizations relying on FreePBX for critical communication infrastructure, especially in sectors like finance, healthcare, and government, face elevated risks. Additionally, compromised telephony systems could be leveraged for further attacks such as social engineering or fraud. The medium severity rating reflects the balance between the ease of exploitation and the scope of impact, but the lack of authentication requirements and the critical nature of telephony systems amplify the potential damage.

Mitigation Recommendations

European organizations should immediately verify their FreePBX Endpoint Manager versions and upgrade to 16.0.96 or 17.0.10 or later. Beyond patching, administrators must enforce strong password policies, replacing any default or weak numeric passwords with complex alphanumeric passwords of sufficient length. Implement rate limiting or account lockout mechanisms on authentication attempts to mitigate brute force attacks. Network segmentation should isolate telephony management interfaces from public or untrusted networks. Monitoring and logging of authentication attempts on the Endpoint Manager should be enabled to detect suspicious activity. Additionally, organizations should conduct regular audits of telephony configurations and credentials, and educate staff on the risks associated with weak telephony passwords. Where feasible, multi-factor authentication should be implemented for administrative access to telephony management systems.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-08T21:46:24.993Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6939f84c7cb4621ebe960e97

Added to database: 12/10/2025, 10:46:36 PM

Last enriched: 2/14/2026, 7:12:25 AM

Last updated: 3/25/2026, 1:33:44 AM

Views: 150

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses