dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-61675

HIGH · 8.6 CVSS v4.0 Published 2025-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
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 Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. In versions prior to 16.0.92 for FreePBX 16 and versions prior to 17.0.6 for FreePBX 17, the Endpoint Manager module contains authenticated SQL injection vulnerabilities affecting multiple parameters in the basestation, model, firmware, and custom extension configuration functionality areas. Authentication with a known username is required to exploit these vulnerabilities. Successful exploitation allows authenticated users to execute arbitrary SQL queries against the database, potentially enabling access to sensitive data or modification of database contents. This issue has been patched in version 16.0.92 for FreePBX 16 and version 17.0.6 for FreePBX 17.

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

Authenticated SQL injection vulnerabilities in FreePBX Endpoint Manager affecting multiple parameters in basestation, model, firmware, and custom extension configuration functionality. The vulnerabilities allow authenticated users to execute arbitrary SQL queries against the database, potentially enabling data exfiltration or modification.

MitigationUpgrade FreePBX Endpoint Manager to version 16.0.92 (for FreePBX 16) or version 17.0.6 (for FreePBX 17) or later. If immediate patching is not possible, restrict access to trusted users only and monitor database activity.

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

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
High
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm Endpoint Manager module is installed
    Run `fwconsole ma list | grep -i endpoint` or check `/var/www/html/admin/modules/endpoint_manager/module.xml` for the module directory
    Affected if Endpoint Manager module exists and is enabled
  2. Determine Endpoint Manager version
    Check the version in `/var/www/html/admin/modules/endpoint_manager/module.xml` or run `fwconsole ma info endpoint`
    Affected if Version is lower than 16.0.92 (for FreePBX 16) or lower than 17.0.6 (for FreePBX 17)
  3. Confirm FreePBX core version
    Run `fwconsole version` or check `/etc/freepbx.conf` to identify if FreePBX 16 or 17 is in use
    Affected if Endpoint Manager version is < 16.0.92 on FreePBX 16, or < 17.0.6 on FreePBX 17
  4. Verify user access to Endpoint Manager
    Check admin user roles and permissions in FreePBX: go to Admin > User Management or inspect the `freepbx_users` and `ampuser` tables in the database
    Affected if Untrusted or low-privilege users have access to the Endpoint Manager module

You are affected if Endpoint Manager is installed with a version below 16.0.92 on FreePBX 16 or below 17.0.6 on FreePBX 17, and untrusted users have access to the module.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade FreePBX Endpoint Manager to version 16.0.92 (for FreePBX 16) or version 17.0.6 (for FreePBX 17) or later. If immediate patching is not possible, restrict access to trusted users only and monitor database activity.

Recommended fix High confidence

FreePBX 16: Endpoint Manager 16.0.92+; FreePBX 17: Endpoint Manager 17.0.6+

  1. Identify the current FreePBX version (16 or 17) and Endpoint Manager module version
  2. For FreePBX 16 systems: upgrade the Endpoint Manager module to version 16.0.92 or later
  3. For FreePBX 17 systems: upgrade the Endpoint Manager module to version 17.0.6 or later
  4. After upgrading, verify the Endpoint Manager module shows the correct patched version
  5. Confirm that the basestation, model, firmware, and custom extension configuration functionality areas work correctly

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

Have this fixed 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 help mitigating

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-61675 — 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-61675 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