CVE-2019-19006
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 · uneditedSangoma FreePBX 115.0.16.26 and below, 14.0.13.11 and below, 13.0.197.13 and below have Incorrect Access Control.
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 confidenceSangoma FreePBX contains an Incorrect Access Control vulnerability affecting versions 15.0.16.26 and below, 14.0.13.11 and below, and 13.0.197.13 and below. The CVSS 9.8 rating indicates this is a network-exploitable, low-complexity vulnerability requiring no authentication, likely allowing unauthorized access to sensitive administrative functions or data within the FreePBX telephony management interface.
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>= 13.0.0.0, <= 13.0.197.13>= 14.0.0.0, <= 14.0.13.11>= 15.0.0.0, <= 15.0.16.26CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed FreePBX versionLog into the FreePBX admin dashboard and navigate to Admin > System Admin > System Overview, or run 'fwconsole ma list' at the command line to see the installed versionAffected if The installed version falls within 13.0.0.0 to 13.0.197.13, 14.0.0.0 to 14.0.13.11, or 15.0.0.0 to 15.0.16.26
-
Verify admin interface requires authenticationAttempt to access FreePBX admin endpoints (such as /admin/config.php or /ajax.php) from an unauthenticated browser session or curl request without passing session credentialsAffected if The admin interface or certain administrative endpoints are accessible without authentication or valid session cookies
-
Check for exposed management portsUse 'netstat -tlnp' or 'ss -tlnp' to list listening services on the system, particularly ports 80, 443, or custom management ports used by FreePBXAffected if The FreePBX web interface is listening on publicly accessible network addresses (0.0.0.0) rather than restricted to localhost or trusted internal IPs
-
Review user role and permission configurationNavigate to Admin > User Management in the FreePBX interface and examine whether all users have appropriate role-based access controls assigned, or inspect the database tables for user privilegesAffected if Users exist with elevated privileges or administrative access that should not have been granted, or role enforcement is not functioning properly
A system is affected if it runs FreePBX versions 13.0.197.13 and below, 14.0.13.11 and below, or 15.0.16.26 and below, AND the admin interface or sensitive endpoints are accessible without proper authorization.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Sangoma FreePBX to versions higher than 15.0.16.26, 14.0.13.11, or 13.0.197.13 respectively. If immediate patching is not possible, restrict network access to the FreePBX management interface using firewall rules or VPN access controls.
FreePBX 15.0.16.27 or later (or the latest 15.x release); alternatively migrate to FreePBX 17 (if available)
- 1. Backup the current FreePBX configuration and all critical data
- 2. Identify the current FreePBX version in the Admin > System Admin > System Info page
- 3. If running FreePBX 13.x: Upgrade to version 13.0.197.14 or later
- 4. If running FreePBX 14.x: Upgrade to version 14.0.13.14 or later (the first version after 14.0.13.11 that includes the fix)
- 5. If running FreePBX 15.x: Upgrade to version 15.0.16.27 or later (the first version after 15.0.16.26 that includes the fix)
- 6. Use the Module Admin interface or command-line fwconsole ma upgradenone to perform the upgrade
- 7. After upgrade, verify that the web interface is accessible and authentication is working correctly
- 8. Review admin accounts and reset passwords as a security precaution
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-19006 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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