Is CVE-2026-46512 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-46512 being exploited in the wild.

How severe is CVE-2026-46512?

Critical severity, with a CVSS score of 9.9, published 16 July 2026.

Is there a fix for CVE-2026-46512?

A patch was published on 2026-05-13: Version 1.6.2 released to fix the injection and an installation regression in 1.6.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-46512 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-46512?

Check whether you run Mwtcmi Frogman 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.

CVE-2026-46512: mwtcmi Frogman code injection in fm_dialplan_apply

CVE-2026-46512 · Severity: critical · CVSS 9.9 · Published 2026-07-16

Frogman, a tool used for managing Asterisk-based phone systems (PBX), contains a vulnerability that allows users with basic write permissions to take full control of the server. By sending specially crafted commands through the system's API, an attacker can bypass intended restrictions to execute arbitrary code or system commands. This could lead to a total compromise of the phone system, unauthorized access to call data, or the ability to use the server for further attacks on the corporate network.

Technologies: Mwtcmi Frogman. Vendors: Mwtcmi.

Quick answers

Is CVE-2026-46512 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-46512 being exploited in the wild.
How severe is CVE-2026-46512?: Critical severity, with a CVSS score of 9.9, published 16 July 2026.
Which products and versions are affected?: Mwtcmi Frogman < 1.6.2.
Is there a fix for CVE-2026-46512?: A patch was published on 2026-05-13: Version 1.6.2 released to fix the injection and an installation regression in 1.6.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46512 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-46512?: Check whether you run Mwtcmi Frogman 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

A code injection vulnerability exists in Frogman's fm_dialplan_apply function due to insufficient sanitization of template parameters (such as greeting, dest, and url) before they are written to the Asterisk configuration file (extensions_custom.conf). While the contextName() was sanitized, other parameters were interpolated raw, allowing a caller with PERM_WRITE privileges to use newlines and special characters to inject arbitrary Asterisk directives. This includes dangerous functions like System() and SHELL(), which grant the attacker root-equivalent shell access on the PBX host. The vulnerability is fixed in version 1.6.2 by implementing strict whitelist validation for all template parameters and a framework-level rejection of control characters.

Affected products

mwtcmi frogman < 1.6.2

Timeline

2026-05-13: disclosed: Disclosed via FreePBX community forum
2026-05-13: patched: Version 1.6.2 released to fix the injection and an installation regression in 1.6.1
2026-07-16: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.