dbcve.org
FreepbxApplication · Sangoma

CVE-2025-66039

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 16.0.44 / 17.0.23 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions are vulnerable to authentication bypass when the authentication type is set to "webserver." When providing an Authorization header with an arbitrary value, a session is associated with the target user regardless of valid credentials. This issue is fixed in versions 16.0.44 and 17.0.23.

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

FreePBX Endpoint Manager versions prior to 16.0.44 and 17.0.23 contain an authentication bypass vulnerability when the authentication type is configured as 'webserver.' An attacker can send an Authorization header with an arbitrary value to associate a session with any target user without providing valid credentials, achieving full authentication bypass.

MitigationUpgrade FreePBX Endpoint Manager to version 16.0.44 or 17.0.23. Alternatively, if immediate upgrading is not feasible, consider changing the authentication type away from 'webserver' to a more secure method until the patch can be applied.

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:< 16.0.44>= 17.0.1, < 17.0.23

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify the installed FreePBX Endpoint Manager version
    In the FreePBX admin interface, navigate to the Endpoint Manager module page, or check the module version via CLI using 'fwconsole ma list | grep endpoint' or by inspecting the file /var/www/html/admin/modules/endpoint_manager/Endpointman_Config.class.php for the version constant
    Affected if The installed version is less than 16.0.44, or greater than or equal to 17.0.1 but less than 17.0.23
  2. Verify the authentication type configuration
    In FreePBX admin, go to Settings > Endpoint Manager > General Settings > Authentication Type, or inspect the database table 'endpoint_manager_settings' for the 'auth_type' or 'auth' configuration key
    Affected if The authentication type is set to 'webserver' (this setting must be enabled for the vulnerability to be exploitable)
  3. Inspect access logs for suspicious Authorization header usage
    Review the web server access logs (typically /var/log/httpd/access_log or /var/log/nginx/access.log) for requests containing arbitrary values in the Authorization header that result in authenticated session establishment
    Affected if Any entries show successful authentication responses (HTTP 200) following requests with arbitrary Authorization header values that do not correspond to valid credentials

You are affected if your FreePBX Endpoint Manager version is vulnerable (below 16.0.44 or between 17.0.1 and 17.0.22) AND the authentication type is configured to 'webserver', allowing potential unauthenticated access via arbitrary Authorization headers.

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 16.0.44 / 17.0.23 or later
Fixed in 16.0.4417.0.23
Vendor patch github.com →
Interim mitigation

Upgrade FreePBX Endpoint Manager to version 16.0.44 or 17.0.23. Alternatively, if immediate upgrading is not feasible, consider changing the authentication type away from 'webserver' to a more secure method until the patch can be applied.

Recommended fix High confidence

FreePBX Endpoint Manager 16.0.44 (for 16.x branch) or 17.0.23 (for 17.x branch)

  1. Identify your current FreePBX Endpoint Manager version in the FreePBX admin interface under Admin > Modules > Endpoint Manager
  2. Determine which major version branch you are running (16.x or 17.x)
  3. For FreePBX 16.x systems: Upgrade Endpoint Manager to version 16.0.44 or later
  4. For FreePBX 17.x systems: Upgrade Endpoint Manager to version 17.0.23 or later
  5. Access the FreePBX admin interface and navigate to Admin > Module Admin
  6. Click 'Check Online' to refresh the module list
  7. Locate Endpoint Manager in the list and click 'Upgrade' to install the fixed version
  8. Alternatively, use the CLI command: fwconsole ma upgrade endpoint_manager

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

Fix this in Freepbx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.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-2025-66039 — 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-2025-66039 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