dbcve.org
Freepbx Linux 7Application · Sangoma

CVE-2023-26567

HIGH · 8.1 CVSS v3.1 Published 2023-04-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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
Sangoma FreePBX 1805 through 2302 (when obtained as a ,.ISO file) places AMPDBUSER, AMPDBPASS, AMPMGRUSER, and AMPMGRPASS in the list of global variables. This exposes cleartext authentication credentials for the Asterisk Database (MariaDB/MySQL) and Asterisk Manager Interface. For example, an attacker can make a /ari/asterisk/variable?variable=AMPDBPASS API call.

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 1805-2302 store database and manager credentials (AMPDBPASS, AMPDBUSER, AMPMGRUSER, AMPMGRPASS) as global variables accessible through the Asterisk ARI API endpoint, allowing unauthenticated attackers to retrieve cleartext authentication credentials for the MariaDB/MySQL database and Asterisk Manager Interface via a simple API call.

MitigationUpgrade FreePBX to a version beyond 2302 that has this vulnerability patched, or implement network-level access controls to restrict the ARI API to trusted sources only.

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
Freepbx Linux 7Application
Affected:= 1805= 1904= 1910= 2002= 2008= 2011= 2104= 2105= 2109= 2112= 2201= 2202

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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
    Run 'fwconsole ma list' or check /etc/freepbx.conf for the version string. Compare against affected versions 1805 through 2302.
    Affected if The installed version falls within 1805-2302 inclusive
  2. Confirm Asterisk ARI API is enabled
    Check the Asterisk manager configuration file (manager.conf) for 'enabled = yes' under the [general] section, and verify ARI is configured in /etc/asterisk/ari.conf. The ARI endpoint is typically accessible on port 8088 by default.
    Affected if ARI API is enabled and accessible on the network
  3. Test ARI API for credential exposure
    Make an unauthenticated HTTP GET request to the ARI API endpoints (e.g., curl http://<asterisk-ip>:8088/ari/api-docs or similar ARI endpoints). Look for response data containing global variables AMPDBPASS, AMPDBUSER, AMPMGRUSER, or AMPMGRPASS.
    Affected if The API returns any of the credential variables (AMPDBPASS, AMPDBUSER, AMPMGRUSER, AMPMGRPASS) in plain text without authentication
  4. Verify database and manager credentials are exposed
    Review the raw API response from the ARI endpoint. Search for strings matching the credential variable names in cleartext format.
    Affected if Credentials for MariaDB/MySQL or Asterisk Manager Interface are visible in the ARI API response

If FreePBX version is 1805-2302 and the Asterisk ARI API is exposed, an unauthenticated attacker can retrieve database and manager credentials through the ARI endpoint.

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

Upgrade FreePBX to a version beyond 2302 that has this vulnerability patched, or implement network-level access controls to restrict the ARI API to trusted sources only.

Recommended fix Moderate confidence

FreePBX 2303 or later (latest stable SNG7 release)

  1. 1. Identify current FreePBX version by checking /etc/freepbx.conf or the FreePBX admin dashboard
  2. 2. Confirm vulnerability by testing if /ari/asterisk/variable?variable=AMPDBPASS returns credentials (do not expose these)
  3. 3. Backup current FreePBX configuration and database using fwconsole backup or mysqldump
  4. 4. Download the latest stable FreePBX ISO from www.sangoma.com or www.freepbx.org
  5. 5. Perform a fresh installation or follow Sangoma's upgrade documentation for your deployment type
  6. 6. After upgrade, verify the vulnerability is fixed by confirming /ari/asterisk/variable endpoint no longer exposes AMPDBUSER, AMPDBPASS, AMPMGRUSER, or AMPMGRPASS
  7. 7. Restore configuration from backup and update any integration credentials as needed
Caveat Fresh install or in-place upgrade may require reconfiguration of extensions, routes, and third-party modules; ensure backup includes all custom configurations

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

Fix this in Freepbx Linux 7 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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