CVE-2026-46515: CWE-862: Missing Authorization in mwtcmi frogman
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.
AI Analysis
Technical Summary
Frogman, a headless PBX control system via MCP and HTTP API, suffers from a missing authorization vulnerability (CWE-862) in versions before 1.6.3. Users with limited PERM_READ privileges could call multiple sensitive functions such as 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. These calls expose critical secrets including AMI manager credentials, outbound dial PINs, Asterisk dialplan contexts, root SSH commands, backup artifact locations, call detail records, arbitrary saved GraphQL queries, and raw AMI endpoint dumps with SIP passwords and OAuth secrets. The vulnerability has a CVSS 4.0 score of 9.3 (critical) and is fixed in version 1.6.3.
Potential Impact
Exploitation allows an attacker with PERM_READ access to retrieve highly sensitive information such as AMI manager secrets, outbound dial PINs, root SSH commands, and SIP credentials. This could lead to unauthorized control over PBX systems, exposure of call records, and compromise of underlying infrastructure. The vulnerability significantly elevates the risk of unauthorized access and data leakage within affected frogman deployments.
Mitigation Recommendations
Upgrade frogman to version 1.6.3 or later, where this missing authorization vulnerability is fixed. No other mitigation or temporary workaround is documented. Patch status is not explicitly stated but the fix is included in version 1.6.3.
CVE-2026-46515: CWE-862: Missing Authorization in mwtcmi frogman
Description
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.
CVSS v4.0
Score 9.3critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Frogman, a headless PBX control system via MCP and HTTP API, suffers from a missing authorization vulnerability (CWE-862) in versions before 1.6.3. Users with limited PERM_READ privileges could call multiple sensitive functions such as 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. These calls expose critical secrets including AMI manager credentials, outbound dial PINs, Asterisk dialplan contexts, root SSH commands, backup artifact locations, call detail records, arbitrary saved GraphQL queries, and raw AMI endpoint dumps with SIP passwords and OAuth secrets. The vulnerability has a CVSS 4.0 score of 9.3 (critical) and is fixed in version 1.6.3.
Potential Impact
Exploitation allows an attacker with PERM_READ access to retrieve highly sensitive information such as AMI manager secrets, outbound dial PINs, root SSH commands, and SIP credentials. This could lead to unauthorized control over PBX systems, exposure of call records, and compromise of underlying infrastructure. The vulnerability significantly elevates the risk of unauthorized access and data leakage within affected frogman deployments.
Mitigation Recommendations
Upgrade frogman to version 1.6.3 or later, where this missing authorization vulnerability is fixed. No other mitigation or temporary workaround is documented. Patch status is not explicitly stated but the fix is included in version 1.6.3.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-14T19:12:32.754Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a59206068715ace437c3f0d
Added to database: 07/16/2026, 18:18:08 UTC
Last enriched: 07/16/2026, 18:32:49 UTC
Last updated: 07/16/2026, 19:26:21 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.