dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 19 Sep 2025.
FreepbxApplication · Sangoma

CVE-2025-57819

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-28
Fix available
A fix is available. Upgrade to 15.0.66 / 16.0.89 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges 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 is an open-source web-based graphical user interface. FreePBX 15, 16, and 17 endpoints are vulnerable due to insufficiently sanitized user-supplied data allowing unauthenticated access to FreePBX Administrator leading to arbitrary database manipulation and remote code execution. This issue has been patched in endpoint versions 15.0.66, 16.0.89, and 17.0.3.

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 versions 15, 16, and 17 contain an unauthenticated remote code execution vulnerability due to insufficient sanitization of user-supplied data. Attackers can gain unauthorized access to the FreePBX Administrator interface without credentials, enabling arbitrary database manipulation and remote code execution.

MitigationUpgrade FreePBX to version 15.0.66, 16.0.89, or 17.0.3 or later. If immediate patching is not feasible, restrict network access to the FreePBX management interface to minimize exposure.

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:>= 15.0, < 15.0.66>= 16.0, < 16.0.89>= 17.0, < 17.0.3

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 FreePBX version
    Log into the FreePBX admin dashboard and navigate to the Admin > System Admin > About page, or run the command line tool 'fwconsole version' or 'amportal a ma show version' to retrieve the installed version number
    Affected if The installed version falls within any of these ranges: 15.0.0 to 15.0.65, 16.0.0 to 16.0.88, or 17.0.0 to 17.0.2
  2. Confirm FreePBX admin interface accessibility
    Verify whether the FreePBX HTTP/HTTPS management interface is reachable from the network. Attempt to access the login page from an untrusted network segment or external IP address without providing credentials
    Affected if The admin interface is accessible from untrusted networks without authentication required
  3. Check for unauthorized database access
    Review FreePBX Asterisk logs (/var/log/asterisk/full or /var/log/asterisk/cdr) and system authentication logs for unusual SQL commands or unexpected admin sessions occurring at unexpected times
    Affected if Logs contain SQL commands or database interactions that were not initiated by legitimate administrators, or unexpected admin sessions appear in the logs

If your FreePBX version is below 15.0.66, 16.0.89, or 17.0.3 AND the admin interface is network-accessible, you are likely affected by this vulnerability.

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 15.0.66 / 16.0.89 / 17.0.3 or later
Fixed in 15.0.6616.0.8917.0.3
Interim mitigation

Upgrade FreePBX to version 15.0.66, 16.0.89, or 17.0.3 or later. If immediate patching is not feasible, restrict network access to the FreePBX management interface to minimize exposure.

Recommended fix High confidence

FreePBX 15.0.66, 16.0.89, or 17.0.3 (depending on your major version)

  1. 1. Backup the FreePBX system and database before starting the upgrade
  2. 2. Identify the currently installed FreePBX major version (15, 16, or 17)
  3. 3. For FreePBX 15.x: upgrade to version 15.0.66 or later
  4. 4. For FreePBX 16.x: upgrade to version 16.0.89 or later
  5. 5. For FreePBX 17.x: upgrade to version 17.0.3 or later
  6. 6. Use the official FreePBX upgrade framework or module admin to perform the upgrade
  7. 7. After upgrade, verify the system is functional and the vulnerability is patched
Caveat Review FreePBX release notes for any configuration or compatibility changes between versions

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

Fix this in Freepbx Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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