CVE-2026-46376
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 · uneditedFreePBX is an open source IP PBX. From 15.0.42 to before 16.0.45 and 17.0.7, unauthenticated users may be able to access the User Control Panel (UCP) using hard-coded initial template credentials if these were not immediately changed by the Administrator who enabled UCP. Authenticated access to ACP is required for the initial setup of UCP generic templates, but after that, without further steps by the admin, unauthenticated users may be able to gain access. This vulnerability is fixed in 16.0.45 and 17.0.7.
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 confidenceFreePBX contains hard-coded initial template credentials for the User Control Panel (UCP) that are set when an administrator enables UCP. If these default credentials are not immediately changed by the administrator, unauthenticated remote attackers can access the UCP without any authentication, potentially gaining full control over the IP PBX system.
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< 16.0.45>= 17.0, < 17.0.7CVSS 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 FreePBX versionRun 'fwconsole ma list' or check /etc/freepbx.conf for the version string. Compare against affected ranges: < 16.0.45, >= 17.0 but < 17.0.7Affected if Installed version falls within 15.0.42 through 16.0.44, or is 17.0.x prior to 17.0.7
-
Verify if UCP module is enabledRun 'fwconsole ucp status' or check the UCP module status in the FreePBX admin interface under Admin > User Control PanelAffected if UCP module is enabled and running
-
Inspect UCP template configuration for default credentialsExamine UCP configuration files in /var/www/html/admin/modules/ucp/ or the database for user accounts. Look for template-created accounts with default or unchanged passwordsAffected if Default/template UCP accounts exist with initial credentials that have not been changed by an administrator
You are affected if FreePBX is version 15.0.42-16.0.44 or 17.0.x prior to 17.0.7, UCP is enabled, and default template credentials in UCP have not been changed from their initial values.
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 · scoped16.0.4517.0.7
Upgrade FreePBX to version 16.0.45 or 17.0.7 or later to obtain the patch, and ensure any default UCP template credentials are changed immediately if patching is delayed.
FreePBX 16.0.45 or FreePBX 17.0.7
- Upgrade FreePBX to version 16.0.45 or higher
- OR
- Upgrade FreePBX to version 17.0.7 or higher
- Consult FreePBX official upgrade documentation for your current version for specific upgrade procedures
- After upgrade, verify UCP access controls are functioning correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46376 — 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-2026-46376 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