Frogman: API tokens stored in plaintext
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-256.
Summary
Frogman provides headless PBX control through MCP and HTTP API. Prior to 1.6.2, Frogman stored API tokens generated by Tools/CreateApiToken.php:33-36 as raw bin2hex(random_bytes(32)) strings in oc_api_tokens, and Frogman.class.php:78 authenticated the X-Frogman-Token header by comparing it with the stored raw value, allowing database read access to recover reusable active tokens at their assigned permission level, including admin. This issue is fixed in version 1.6.2.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA frogman (mwtcmi) Fixed in 1.6.2
Timeline
- 2026-10-02 Threatist record created from CVE-2026-46513
References
More mwtcmi vulnerabilities
- TI-2026-34201 Frogman: Dialplan template parameters interpolated into extensions_custom.conf without escaping CVSS 3.1CRITICAL 9.9
- TI-2026-34204 Frogman: Multiple read-tier tools expose admin-grade data and arbitrary GraphQL execution CVSS 4.0CRITICAL 9.3
- TI-2026-34203 Frogman: Plaintext passwords and secrets persisted to audit log CVSS 3.1MEDIUM 6.5
- TI-2026-34205 Frogman vulnerable to stored XSS in chat console formatter (escalation vector in multi-admin deployments) CVSS 4.0MEDIUM 4.8
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences