# CVE-2026-46512: Frogman: Dialplan template parameters interpolated into extensions_custom.conf without escaping

> An attacker with write permissions can inject arbitrary Asterisk directives into configuration files, leading to remote code execution.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 18 Jul 2026
- **Also known as:** GHSA-pxfc-q72v-jh8m

## What is CVE-2026-46512?

CVE-2026-46512 is a critical code injection vulnerability in mwtcmi frogman, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-46512?


## How do I fix CVE-2026-46512?

No fix has been published for CVE-2026-46512 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-46512 being exploited?

There is no known exploitation of CVE-2026-46512 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46512 and fix it if it is affected.

What it is: CVE-2026-46512 is a critical code injection vulnerability in mwtcmi frogman, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46512 in the wild and no public exploit code.

Affected product: mwtcmi frogman. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46512/ (Markdown: https://insights.sbomify.com/CVE-2026-46512/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46512
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46512
- OSV: https://osv.dev/vulnerability/CVE-2026-46512

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46512/
Summaries are generated and may contain mistakes; the official description above is the record.