Quick answers
- Is CVE-2026-45562 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45562 being exploited in the wild.
- How severe is CVE-2026-45562?
- Informational severity, published 28 September 2026.
- Which products and versions are affected?
- FreePBX 16 before 16.0.4, 17 before 17.0.6.
- Is there a fix for CVE-2026-45562?
- A patch was published on 2026: Versions 16.0.4 and 17.0.6 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45562 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-45562?
- Check whether you run FreePBX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Music on Hold module fails to sanitize POST parameters defining custom Asterisk applications before storing them in the database and writing them to musiconhold_additional.conf without validation. Asterisk then executes these configuration directives, allowing authenticated attackers to inject arbitrary OS commands. Attack requires valid FreePBX administrator credentials and network access to the Admin Control Panel; fixes are available in versions 16.0.4 and 17.0.6.
Affected products
- FreePBX FreePBX 16 before 16.0.4, 17 before 17.0.6
Timeline
- 2026-09-28: disclosed
- 2026: patched: Versions 16.0.4 and 17.0.6 released