Security readout for executives and security teams
Plain-English summary
Frogman versions before 1.6.2 can let an already authorized write user turn dialplan template input into dangerous Asterisk configuration. In business terms, a compromised or malicious automation/API account could potentially affect PBX confidentiality, integrity, and availability. The vendor lists this as critical and fixed in 1.6.2.
Executive priority
Treat as urgent for any production PBX automation environment using Frogman before 1.6.2. Prioritize upgrade and access review because the vulnerability crosses from application input into telephony control configuration with critical confidentiality, integrity, and availability impact.
Technical view
fm_dialplan_apply accepted template parameters that were written into extensions_custom.conf without adequate escaping. Only contextName() was sanitized, leaving fields such as greeting, dest, url, extension, code, and file able to inject arbitrary Asterisk directives. The issue requires PERM_WRITE and confirm:true, but has network reachability and high impact per CVSS 9.9.
Likely exposure
Exposure is limited to mwtcmi Frogman deployments before 1.6.2 where MCP or HTTP API users with PERM_WRITE can invoke fm_dialplan_apply. The source bundle does not identify hosted services, default exposure, or affected downstream distributions.
Exploitation context
The provided sources do not report active exploitation, and KEV is false. Exploitation requires an authenticated or otherwise authorized caller with PERM_WRITE and confirm:true. The impact is still severe because successful abuse can inject Asterisk directives into live dialplan configuration.
Researcher notes
Evidence comes from the CVE record, GitHub advisory, fix commit, and release references. The vulnerability is described as CWE-94 code injection through unescaped template parameters. Public sources provided here do not include exploit proof, exploitation telemetry, or detailed deployment prevalence.
Mitigation direction
- Upgrade Frogman to version 1.6.2 or later.
- Restrict PERM_WRITE access to trusted administrative users only.
- Review vendor advisory before applying compensating controls beyond upgrade.
- Audit recent generated dialplan configuration for unexpected directives.
- Limit MCP and HTTP API reachability to trusted networks where feasible.
Validation and detection
- Inventory all Frogman deployments and record installed versions.
- Confirm vulnerable instances are upgraded to 1.6.2 or later.
- Review accounts and tokens with PERM_WRITE permission.
- Inspect extensions_custom.conf for unexpected custom Asterisk directives.
- Check logs for recent fm_dialplan_apply activity by write-capable users.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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.
Open ATT&CK lookupCVE-2026-46512 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/mwtcmi/frogman/security/advisories/GHSA-pxfc-q72v-jh8mCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/mwtcmi/frogman/commit/36a05ffa2df1d256b6f6f7c3b66ef77ebe3e458aCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/mwtcmi/frogman/releases/tag/v1.6.1CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/mwtcmi/frogman/releases/tag/v1.6.2CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.