Loading vulnerability…
Missing Authorization in Frogman PERM_READ API Functions
CVE-2026-46515 is a missing authorization vulnerability in Frogman, a headless PBX control platform exposing MCP and HTTP APIs. In versions prior to 1.6.3, accounts granted only PERM_READ privileges could invoke multiple sensitive functions, including 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, without sufficient authorization checks. As a result, low-privileged users could access highly sensitive administrative and telephony data, including AMI manager credentials and secrets, outbound dialing PIN sets, complete Asterisk dialplan context, root SSH connection command details, backup-related information, call detail record history, and raw AMI endpoint data containing SIP authentication material. The flaw also permitted execution of saved GraphQL queries through a read-level permission boundary, extending the issue beyond passive disclosure into unauthorized access to application functionality. The vulnerability is fixed in Frogman 1.6.3.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows a user with only PERM_READ access to retrieve sensitive PBX, telephony, and infrastructure data that should be restricted to higher-privileged roles. Exposed information can include administrative secrets, SIP authentication material, outbound dialing PINs, dialplan logic, backup metadata, and call history, creating substantial confidentiality impact. Because the flaw also enables unauthorized execution of saved GraphQL queries and access to operational configuration details, it can also affect integrity by allowing low-privileged users to exercise functionality beyond their intended role and potentially leverage disclosed secrets for follow-on compromise of connected systems or services.
If you can’t patch tonight, do this now.
If immediate upgrade is not possible, restrict assignment of PERM_READ to only strictly necessary users and minimize network exposure to the MCP and HTTP APIs. Disable or otherwise gate access to the affected functions where operationally feasible, and monitor for unauthorized use of read-tier accounts against administrative, diagnostic, and query-execution endpoints. Audit for exposure of telephony credentials, dialplan information, backup metadata, and call records, and rotate sensitive material as a precaution. Additional compensating controls include limiting API access through segmentation, strong authentication, and least-privilege role review.
Patch, then assume compromise.
Upgrade Frogman to version 1.6.3 or later, where the affected functions are no longer accessible with insufficient authorization. Review role-based access controls to ensure PERM_READ accounts cannot invoke privileged administrative, diagnostic, configuration, or query-execution functions. After patching, rotate any exposed credentials or secrets, including AMI-related secrets, SIP authentication material, outbound dialing PINs, and any other sensitive values that may have been disclosed. Review backup handling and administrative access paths that may have been exposed through the vulnerable endpoints.
No public exploits tracked yet. Mallory keeps watching.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.