CVE-2026-46515: Frogman: Multiple read-tier tools expose admin-grade data and arbitrary GraphQL execution
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.
Security readout for executives and security teams
Plain-English summary
Frogman before 1.6.3 allowed users with read-only permission to retrieve highly sensitive PBX administration data. That could expose call records, manager secrets, dialing PINs, dialplan details, backup paths, and connection information. The vulnerability is fixed in 1.6.3, and the bundle does not show active exploitation.
Executive priority
Treat this as an urgent patch and credential-review item for any Frogman-managed PBX environment. The business concern is sensitive telephony administration data exposure, not confirmed mass exploitation.
Technical view
This is an authorization failure in Frogman’s MCP and HTTP API. PERM_READ could access multiple tools that returned admin-grade data or executed saved GraphQL queries. Affected versions are mwtcmi frogman before 1.6.3. The CVSS 4.0 score is 9.3 and CWE-862 is listed.
Likely exposure
Exposure is most likely in organizations running Frogman below 1.6.3 with MCP or HTTP API users assigned PERM_READ. PBX environments with stored AMI, SIP, OAuth, SSH, dial PIN, CDR, backup, or dialplan data are the relevant scope.
Exploitation context
The source bundle supports low-privilege authenticated misuse, not unauthenticated exploitation. KEV is false, and no cited source states active exploitation. The risk is still severe because read-tier access could reveal secrets and operational PBX data.
Researcher notes
The advisory names 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. Evidence indicates an authorization boundary failure fixed in 1.6.3; exploit availability is not established in the supplied sources.
Mitigation direction
Upgrade Frogman to version 1.6.3 or later.
Review the GitHub advisory and release notes for vendor guidance.
Restrict MCP and HTTP API access to trusted users and networks.
Audit PERM_READ accounts and remove unnecessary access.
Rotate exposed AMI, SIP, OAuth, SSH, and dialing secrets if access is suspected.
Validation and detection
Inventory Frogman deployments and confirm installed versions.
Review accounts or tokens with PERM_READ access.
Check logs for use of the affected read-tier tools.
Confirm sensitive tool outputs now require appropriate authorization.
Review saved GraphQL query access and execution permissions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-862 · source CWE mapping
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.