# FreePBX Security Updates, August to September 2026: What to Update and How to Check

Source: https://srvscripts.com/guides/freepbx-security-updates-2026/
Updated: 2026-11-02
Publisher: srvScripts (https://srvscripts.com/)

**Short answer:** FreePBX security updates fixed 17 advisories published between 21 August and 29 September 2026, in the framework, backup, ucp, sangomartapi (Sangoma Connect), recordings, cel, recording_report, sipstation, contactmanager and pinsets modules. On FreePBX 17 you are covered when framework is at least 17.0.33, backup 17.0.13, sangomartapi 17.0.29 and ucp 17.0.10 (full list below). Check with `fwconsole ma list` or our read-only script, update with `fwconsole ma upgradeall`, then `fwconsole reload`. Asterisk itself had no new advisories in this period. (Reviewed October 2026.)

In short: FreePBX published 17 security advisories between 21 August and 29 September 2026, in the framework, backup, ucp, sangomartapi (Sangoma Connect), recordings, cel, recording_report, sipstation…

Most of these advisories need a logged-in user, but several only need a UCP (user portal) account, one needs nothing more than an incoming call, and the most serious one needs no login at all. We took the list from the official [FreePBX security advisories](https://github.com/FreePBX/security-reporting/security/advisories) on GitHub, checked each fixed version there, and tested a version-check script on our FreePBX 17 lab.

## The advisories and the fixed versions

Dates are the GitHub publication dates; severity is the CVSS v4 score shown on each advisory. None of them had a CVE ID or an entry in CISA’s Known Exploited Vulnerabilities list when we checked on 21 October 2026, and no advisory says it was exploited in the wild.

| Published | Advisory | Module | Fixed (17) | Fixed (16) | Severity | Who can use it |
| --- | --- | --- | --- | --- | --- | --- |
| 21 Aug | GHSA-h9vq-j62m-6m73 | sangomartapi | 17.0.26 | 16.0.55 | Critical 9.3 | No login: SQL injection in the Sangoma Connect RT API login (remote code execution) |
| 21 Aug | GHSA-rgq3-mgw4-rcfh | ucp | 17.0.10 | 16.0.41 | High 8.8 | No login: missing authorization lets anyone reset or overwrite users’ UCP data |
| 24 Aug | GHSA-2f5p-xvrc-j2wf | sangomartapi | 17.0.26 | 16.0.55 | High 8.7 | Logged in: remote code execution via FindMeFollowMe in Sangoma Connect |
| 24 Aug | GHSA-pw3c-6wm2-mxg4 | framework | 17.0.31 | 16.0.48 | High 8.6 | Admin with limited rights can escalate privileges |
| 24 Aug | GHSA-rvwr-xrpc-4hf4 | backup | 17.0.12 | 16.0.74 | High 8.6 | Logged in: backup metadata hooks execution bypass |
| 24 Aug | GHSA-65g4-v227-g8m3 | backup | 17.0.12 | 16.0.74 | High 8.6 | Logged in: command injection via restore file name |
| 31 Aug | GHSA-m8mc-g8fg-4765 | framework | 17.0.32 | 16.0.49 | High 8.6 | Broken access control in the GraphQL API |
| 17 Sep | GHSA-3hr3-9whj-655f | framework | 17.0.33 | 16.0.50 | High 8.7 | Any UCP user: remote code execution via AMI |
| 17 Sep | GHSA-fwpm-x5rh-2pr6 | backup | 17.0.13 | 16.0.75 | High 8.7 | Logged in: code execution via unsafe unserialize in restore |
| 17 Sep | GHSA-5457-hm39-pcfc | backup | 17.0.13 | 16.0.76 | High 8.6 | Admin: root command injection in GraphQL restoreBackup |
| 17 Sep | GHSA-9cjf-xw9x-55hh | recordings | 17.0.6 | 16.0.21 | High 8.6 | Admin: command execution via dialplan injection |
| 17 Sep | GHSA-hq6g-xv43-3v87 | cel | 17.0.3 | 16.0.21 | High 8.7 | No login: caller ID of an incoming call becomes stored XSS in CEL Reports |
| 17 Sep | GHSA-x6qq-4527-j9gf | recording_report | 17.0.3.16 | 16.0.33.8 | Medium 6.9 | Admin can read any file via the call recording report |
| 29 Sep | GHSA-3827-8r8q-362j | sangomartapi | 17.0.29 | 16.0.57 | High 7.1 | Any UCP user can read the whole database (SQL injection) |
| 29 Sep | GHSA-pq27-pw7r-4x8j | sipstation | 17.0.4 | – | High 8.6 | Admin: SQL injection via SIPSTATION |
| 29 Sep | GHSA-7wg2-66mh-g7mg | pinsets | 17.0.4 | 16.0.9 | High 8.6 | Logged in: privilege escalation via SQL injection in Pinsets |
| 29 Sep | GHSA-j82w-j6cr-56m6 | contactmanager | 17.0.8 | 16.0.29 | Medium 5.3 | UCP user can change other users’ contacts |

For each module, the highest version in the table is the one that covers all of its advisories. On FreePBX 17 that is:

| Module | Minimum version on FreePBX 17 |
| --- | --- |
| framework | 17.0.33 |
| backup | 17.0.13 |
| sangomartapi | 17.0.29 |
| ucp | 17.0.10 |
| recordings | 17.0.6 |
| cel | 17.0.3 |
| recording_report | 17.0.3.16 |
| sipstation | 17.0.4 |
| contactmanager | 17.0.8 |
| pinsets | 17.0.4 |

On FreePBX 16, use the “Fixed (16)” column, taking the highest value per module (for example backup 16.0.76 and framework 16.0.50). FreePBX 16 still received fixes for these, but plan the move: see [upgrading FreePBX 16 to 17](https://srvscripts.com/guides/upgrade-freepbx-16-to-17/).

## Check your PBX

`fwconsole ma list` shows every installed module with its version and status. To compare the ten modules above in one go, this read-only script prints each one with the fixed version. It exits 0 when everything is covered, 1 if anything needs an update, and 3 if it could not tell (fwconsole failed, the module list could not be read, or a version did not look like a FreePBX 17 version), so a monitoring check never treats a read problem as “OK”:

```
#!/bin/bash
# fpbx-advisory-check.sh - FreePBX 17: compare installed module versions with the
# fixed versions from the advisories of 21 Aug - 29 Sep 2026. Read-only. Run as root.
# Exit: 0 all OK, 1 at least one update needed, 3 something could not be checked.
set -u
FIXED="framework 17.0.33
backup 17.0.13
recordings 17.0.6
cel 17.0.3
recording_report 17.0.3.16
sangomartapi 17.0.29
sipstation 17.0.4
contactmanager 17.0.8
pinsets 17.0.4
ucp 17.0.10"
list=$(fwconsole ma list 2>/dev/null) || { echo "UNKNOWN: fwconsole ma list failed (run as root on FreePBX 17)"; exit 3; }
# Rows look like: | framework | 17.0.33.2 | Enabled | GPLv2+ | ...
rows=$(printf '%s\n' "$list" | awk -F'|' 'NF>=4 {m=$2; v=$3; gsub(/ /,"",m); gsub(/ /,"",v); if (m!="" && m!="Module") print}')
if [ "$(printf '%s\n' "$rows" | grep -c 'framework')" -ne 1 ]; then
  echo "UNKNOWN: could not read the module list (framework not found); check: fwconsole ma list"; exit 3
fi
need=0; unknown=0
printf '%-18s %-12s %-12s %s\n' MODULE INSTALLED FIXED_IN STATUS
while read -r mod fix; do
  info=$(printf '%s\n' "$rows" | awk -F'|' -v m="$mod" '{a=$2; gsub(/ /,"",a)} a==m {v=$3; t=$4; gsub(/ /,"",v); gsub(/^ +| +$/,"",t); print v "|" t; exit}')
  if [ -z "$info" ]; then printf '%-18s %-12s %-12s %s\n' "$mod" "-" "$fix" "not installed"; continue; fi
  ver=${info%%|*}; st=${info#*|}
  if ! [[ "$ver" =~ ^17\.[0-9]+(\.[0-9]+)*$ ]]; then
    s="UNKNOWN (version '$ver' is not a FreePBX 17 version)"; unknown=1
  elif [ "$(printf '%s\n%s\n' "$fix" "$ver" | sort -V | head -1)" = "$fix" ]; then s="OK"
  else s="UPDATE NEEDED"; need=1; fi
  [ "$st" != "Enabled" ] && s="$s (${st:-status unknown})"
  printf '%-18s %-12s %-12s %s\n' "$mod" "$ver" "$fix" "$s"
done
