Vulnerability Description
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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/mwtcmi/frogman/commit/b10f314add08c8e7585ba4b27d071b07d026ab5
- https://github.com/mwtcmi/frogman/releases/tag/v1.6.1
- https://github.com/mwtcmi/frogman/releases/tag/v1.6.2
- https://github.com/mwtcmi/frogman/security/advisories/GHSA-9xf5-9ghq-p6cw
FAQ
What is CVE-2026-46513?
CVE-2026-46513 is a vulnerability with a CVSS score of 7.4 (HIGH). 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...
How severe is CVE-2026-46513?
CVE-2026-46513 has been rated HIGH with a CVSS base score of 7.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-46513?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.