CVE REMEDIATION GUIDE
Review reviewCriticalFixed-version data available

CVE-2026-46376 remediation guide

FreePBX security-reporting, freepbx

FreePBX 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.

Open CVE record
ProductFreePBX security-reporting, freepbx
Affected versions>= >= 15.0.42, < 16.0.45, >= >= 17.0.1, < 17.0.7, >= 17.0 < 17.0.7
Fixed versions16.0.45, 17.0.7
Priority basisReview · CVSS 9.3 · EPSS 0.43%
01

Identify the affected asset

Confirm whether FreePBX security-reporting, freepbx is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= >= 15.0.42, < 16.0.45, >= >= 17.0.1, < 17.0.7, >= 17.0 < 17.0.7. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 16.0.45, 17.0.7. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2026-46376 Remediation Guide | SECUFOCUS NOW