Threat Intelligence Database

Frogman provides headless PBX control through MCP and HTTP API. Prior to 1.6.3, PERM_READ access was sufficient to call fm_list_managers, fm_list_pinsets, fm_show_context, fm_get_mcp_config, fm_backup_status, fm_whos_calling, fm_run_saved_query, and fm_diagnose_trunk, exposing AMI manager secrets, outbound dial PINs, full Asterisk dialplan context, root SSH connection commands, backup artifact paths, CDR history, arbitrary saved GraphQL query execution, and raw AMI endpoint dumps containing SIP fields such as password, md5_cred, and oauth_secret. This issue is fixed in version 1.6.3.

Frogman provides headless PBX control through MCP and HTTP API. Prior to 1.6.2, fm_reset_password in Tools/ResetPassword.php:48-53 returned a plaintext password and fm_add_extension in Tools/AddExtension.php:172 returned a plaintext secret; Frogman.class.php:2207-2211 used auditOutcome to JSON-encode those responses into oc_audit_log.detail, allowing any PERM_READ caller with access to fm_audit_search to recover the stored credentials. This issue is fixed in version 1.6.2.

Frogman, a headless PBX control system, stored API tokens as plaintext hex strings in its database prior to version 1.6.2. These tokens, used for authentication via the X-Frogman-Token header, could be recovered by reading the database, potentially exposing active tokens including those with administrative permissions. This vulnerability is identified as CWE-256 and has a CVSS score of 7.4 (high severity). The issue is fixed in Frogman version 1.6.2.

CVE-2026-46512 is a critical code injection vulnerability in mwtcmi frogman prior to version 1.6.2. The vulnerability arises because the fm_dialplan_apply function accepted template parameters that could be used by a PERM_WRITE caller with confirm:true to inject arbitrary Asterisk directives. Only limited sanitization was applied, allowing injection of commands like System(), Set(SHELL(...)), Goto, or Macro. This issue allows an attacker with limited privileges to execute arbitrary code within the Asterisk PBX environment. The vulnerability is fixed in version 1.6.2.