dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-59051

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
The FreePBX Endpoint Manager module includes a Network Scanning feature that provides web-based access to nmap functionality for network device discovery. In Endpoint Manager 16 before 16.0.92 and 17 before 17.0.6, insufficiently sanitized user-supplied input allows authenticated OS command execution as the asterisk user. Authentication with a known username is required. Updating to Endpoint Manager 16.0.92 or 17.0.6 addresses the issue.

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

The FreePBX Endpoint Manager module's Network Scanning feature (which provides web-based access to nmap for network device discovery) contains an OS command injection vulnerability due to insufficient input sanitization. An authenticated attacker with valid credentials can execute arbitrary OS commands as the asterisk user. This affects Endpoint Manager versions 16 before 16.0.92 and 17 before 17.0.6.

MitigationUpdate FreePBX Endpoint Manager to version 16.0.92 or 17.0.6 or later to remediate the command injection vulnerability. Since authentication is required, also review and rotate credentials for any compromised accounts.

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. Verify Endpoint Manager module is installed
    Access FreePBX admin panel and navigate to Admin > Module Admin, or run 'fwconsole ma list' command to list installed modules and locate Endpoint Manager (or endpointman/endpoint_manager)
    Affected if Endpoint Manager module is not found in the module list, then this CVE does not apply
  2. Determine installed Endpoint Manager version
    In FreePBX admin panel, go to Endpoint Manager > Settings and locate the version displayed, or run 'fwconsole ma info endpoint_manager' (or endpointman) to retrieve version information
    Affected if Version is 16.x and below 16.0.92, or version is 17.x and below 17.0.6
  3. Confirm Network Scanning feature is enabled
    In FreePBX admin panel, navigate to Endpoint Manager > Network Scan (or Network Scanning) settings and verify if the feature is active/enabled, or inspect module configuration files for network scanning settings
    Affected if Network Scanning is enabled and configured for use
  4. Verify authenticated user access to Endpoint Manager
    Check user permissions in FreePBX under Admin > User Management to see which users have access to the Endpoint Manager module, or review asterisk ACL configurations
    Affected if Any user account with valid credentials has access to Endpoint Manager module

Your environment is affected if Endpoint Manager is installed with version 16.x below 16.0.92 or version 17.x below 17.0.6, the Network Scanning feature is enabled, and any authenticated user can access 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

Update FreePBX Endpoint Manager to version 16.0.92 or 17.0.6 or later to remediate the command injection vulnerability. Since authentication is required, also review and rotate credentials for any compromised accounts.

Recommended fix High confidence

Endpoint Manager 16.0.92 or 17.0.6 (depending on your major version)

  1. Backup your FreePBX system before performing any updates
  2. Update the FreePBX Endpoint Manager module to version 16.0.92 if running version 16.x
  3. Update the FreePBX Endpoint Manager module to version 17.0.6 if running version 17.x
  4. Verify the module update was successful by checking the module administration page
  5. Confirm the Network Scanning feature functions correctly after the update

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59051 — 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-59051 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