Frogman provides headless PBX control through MCP and HTTP API. Prior to 1.6.2, fm_dialplan_apply accepted template parameters including greeting, dest, url, extension, code, and file, and Tools/DialplanApply.php wrote Dialplan/Templates.php output to extensions_custom.conf while only Dialplan/TemplateBase.php:38-42 sanitized contextName(), allowing a PERM_WRITE caller using confirm:true to inject arbitrary Asterisk directives such as System(), Set(SHELL(...)), Goto, or Macro. This issue is fixed in version 1.6.2.
CVE-2026-46512
This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.9
- EG Score
- 9.9(low)
- EPSS
- —
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 16, 2026
Advisory Details (4)
Auto-updated Jul 16, 2026v1.6.2 — install.php regression fix
Patch available: mwtcmi/frogman v1.6.2
https://github.com/mwtcmi/frogman/releases/tag/v1.6.2v1.6.1 — Security release (superseded by v1.6.2)
Patch available: mwtcmi/frogman v1.6.1
https://github.com/mwtcmi/frogman/releases/tag/v1.6.1commit 36a05ffa2df1 (mwtcmi/frogman)
Patch available: mwtcmi/frogman v1.6.1 (contains commit 36a05ffa2df1)
https://github.com/mwtcmi/frogman/commit/36a05ffa2df1d256b6f6f7c3b66ef77ebe3e458aDialplan template parameters interpolated into extensions_custom.conf without escaping · Advisory · mwtcmi/frogman · GitHub
https://github.com/mwtcmi/frogman/security/advisories/GHSA-pxfc-q72v-jh8mWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-17 02:58 UTCEG score recompute
- 2026-07-16 22:38 UTCEG score recompute
- 2026-07-16 18:19 UTCEG score recompute
- 2026-07-16 18:18 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-94
- CVE-2006-1359NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2005-1921NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2005-3302EG 7.3HIGH
- CVE-2005-1876EG 4.5MEDIUM
- CVE-2003-1599EG 0.0NONE
- CVE-2006-1318EG 0.0EPSS 96%NONE
- CVE-2006-1301EG 0.0EPSS 95%NONE
- CVE-2006-1308EG 0.0EPSS 95%NONE
- CVE-2006-1309EG 0.0EPSS 95%NONE
- CVE-2006-1304EG 0.0EPSS 95%NONE
Frequently asked(4)
What is CVE-2026-46512?
When was CVE-2026-46512 disclosed?
What is the CVSS score of CVE-2026-46512?
How do I remediate CVE-2026-46512?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-46512
Is Your Infrastructure Affected by CVE-2026-46512?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.