dbcve.org
RestappsApplication · Sangoma

CVE-2020-10666

CRITICAL · 9.8 CVSS v3.1 Published 2021-05-31
Fix available
A fix is available. Upgrade to after 15.0.19.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
The restapps (aka Rest Phone apps) module for Sangoma FreePBX and PBXact 13, 14, and 15 through 15.0.19.2 allows remote code execution via a URL variable to an AMI command.

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 · moderate confidence

The restapps module for Sangoma FreePBX and PBXact (versions 13-15 through 15.0.19.2) contains an insecure direct object reference or input validation flaw where URL variables are passed unsanitized directly to Asterisk Manager Interface (AMI) commands, enabling remote attackers to inject arbitrary AMI commands and achieve remote code execution.

MitigationUpgrade the restapps module to a version newer than 15.0.19.2; if immediate patching is not possible, disable the restapps module and implement network-level restrictions on the AMI port (5039) to prevent external access.

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
RestappsApplication
Affected:>= 13.0, <= 13.0.93.2>= 14.0, <= 14.0.22.2>= 15.0, <= 15.0.19.2

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. Verify restapps module is installed
    Run the command 'fwconsole ma list | grep restapps' or check the FreePBX GUI at Admin > Modules to see if restapps appears in the module list
    Affected if The restapps module appears in the module list, indicating it is installed
  2. Check installed restapps version
    Run 'fwconsole ma list | grep restapps' to see the version number, or inspect the module file /var/www/html/admin/modules/restapps/module.xml for the version tag
    Affected if The installed version falls within 13.0 to 13.0.93.2, 14.0 to 14.0.22.2, or 15.0 to 15.0.19.2
  3. Confirm AMI port accessibility
    Check if port 5039 is listening and exposed by running 'netstat -tlnp | grep 5039' or 'ss -tlnp | grep 5039', then verify network accessibility from untrusted interfaces
    Affected if Port 5039 is open and accessible from network interfaces other than localhost or trusted management networks
  4. Verify restapps feature is enabled
    Check the FreePBX GUI under Settings > Rest API Settings or inspect the file /etc/freepbx.conf for restapps-related configuration, or run 'fwconsole restapps status' if the command is available
    Affected if The restapps or REST API feature is enabled and the service is running

A system is affected if the restapps module is installed with a version between 13.0 and 15.0.19.2 and the AMI port 5039 is network-accessible

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 a release after 15.0.19.2
Interim mitigation

Upgrade the restapps module to a version newer than 15.0.19.2; if immediate patching is not possible, disable the restapps module and implement network-level restrictions on the AMI port (5039) to prevent external access.

Recommended fix Moderate confidence

restapps module version > 13.0.93.2 (for FreePBX 13), > 14.0.22.2 (for FreePBX 14), > 15.0.19.2 (for FreePBX 15)

  1. 1. Access the FreePBX admin web interface
  2. 2. Navigate to Admin > Module Admin
  3. 3. Check for updates to the 'restapps' (Rest Phone Apps) module
  4. 4. If an update is available, review the version (should be higher than 13.0.93.2, 14.0.22.2, or 15.0.19.2 depending on your FreePBX version)
  5. 5. Backup the current PBX configuration
  6. 6. Install the updated restapps module
  7. 7. Apply changes and reload the FreePBX configuration
  8. 8. Verify the module is updated by checking the restapps module version in Admin > Modules
Caveat Module updates in FreePBX typically do not introduce breaking changes for basic functionality, but test in a staging environment before production deployment

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

Fix this in Restapps Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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