dbcve.org
FreepbxApplication · Sangoma

CVE-2025-67736

HIGH · 7.2 CVSS v3.1 Published 2025-12-16
Fix available
A fix is available. Upgrade to 16.0.5 / 17.0.5 or later.
See remediation →
78/100
Remediation priority · High
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 module tts (Text to Speech) for FreePBX, an open-source web-based graphical user interface (GUI) that manages Asterisk. Versions prior to 16.0.5 and 17.0.5 are vulnerable to SQL injection by authenticated users with administrator access. Authenticated users with administrative access to the Administrator Control Panel (ACP) can leverage this SQL injection vulnerability to extract sensitive information from the database and execute code on the system as the `asterisk` user with chained elevation to `root` privileges. Users should upgrade to version 16.0.5 or 17.0.5 to receive a fix.

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 tts (Text-to-Speech) module prior to versions 16.0.5 and 17.0.5 contains a SQL injection vulnerability exploitable by authenticated administrators through the web interface. Attackers can inject malicious SQL queries to extract sensitive data from the database and achieve code execution as the asterisk system user, with potential for further root privilege escalation.

MitigationUpgrade the FreePBX tts module to version 16.0.5 or 17.0.5. Until patched, restrict administrative access to trusted personnel and monitor for suspicious SQL query patterns in logs.

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, < 16.0.5>= 17.0, < 17.0.5

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

CVSS:3.1/AV:N/AC:L/PR:H/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 installation and version
    Access the FreePBX admin dashboard or run `freepbx -V` from command line to confirm FreePBX is installed and note the core version
    Affected if FreePBX core version is 16.x or 17.x (the tts module applies to these major versions)
  2. Locate the tts module version
    Navigate to Admin > Module Admin in the FreePBX web interface, or run `fwconsole ma list | grep tts` from the CLI to identify the tts module and its installed version
    Affected if The tts module version is displayed and can be compared to the affected ranges
  3. Compare tts version against vulnerable ranges
    Check if the installed tts version is less than 16.0.5 (for FreePBX 16.x) or less than 17.0.5 (for FreePBX 17.x)
    Affected if tts version is < 16.0.5 on FreePBX 16.x systems OR tts version is < 17.0.5 on FreePBX 17.x systems
  4. Verify web admin interface exposure
    Confirm whether the FreePBX web interface is accessible from network locations beyond localhost, as the vulnerability requires an authenticated administrator session
    Affected if The admin interface is exposed to untrusted networks or users
  5. Review access logs for SQL injection patterns
    Inspect web server access logs (typically /var/log/httpd or /var/log/asterisk) for unusual SQL syntax in tts-related requests from administrator IPs
    Affected if Unusual SQL fragments or error messages appear in logs following tts module requests

You are affected if the FreePBX tts module version is below 16.0.5 on FreePBX 16.x or below 17.0.5 on FreePBX 17.x and the web admin interface is accessible to untrusted users.

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.5 / 17.0.5 or later
Fixed in 16.0.517.0.5
Interim mitigation

Upgrade the FreePBX tts module to version 16.0.5 or 17.0.5. Until patched, restrict administrative access to trusted personnel and monitor for suspicious SQL query patterns in logs.

Recommended fix High confidence

FreePBX 16.0.5 or 17.0.5 (tts module)

  1. 1. Create a complete backup of the FreePBX system including all configurations and databases
  2. 2. Log into the FreePBX Administrator Control Panel (ACP) as an administrator
  3. 3. Navigate to the Module Administration page
  4. 4. Check for available updates for the 'tts' (Text to Speech) module
  5. 5. Update the tts module to version 16.0.5 (for FreePBX 16.x) or version 17.0.5 (for FreePBX 17.x)
  6. 6. Apply all pending updates and confirm the module is upgraded successfully
  7. 7. Restart Asterisk service to ensure the updated module is loaded
  8. 8. Verify the tts module version reflects the update in Module Administration
Caveat Standard FreePBX upgrade precautions apply - ensure full backup before proceeding

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

Fix this in Freepbx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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