VulnSocial

CVE-2026-46513Disclosure

LOWCVSS 7.4 · HIGH

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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.

Back to dashboard
0.0/ 10 priority

Sources & remediation

Other references
Weakness type (CWE)
CWE-256

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 2 mentions across 1 observed day

What's happening

  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • 2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-07-16: 2Technical Details · 2026-07-16: 207-16
Signal classification1 categories
Disclosure
2100.0%
Referenced assets2 URLs
By indicator
Full discourse2 posts
  • Infoflowcloud@infoflowcloud
    Disclosure

    🚨*CVE* CVE-2026-46513 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(r… https://www.cve.org/CVERecord?id=CVE-2026-46513 ----- Traducción: CVE-2026-46513 Fro… http://infoflow.cloud`

    Post summary

    The snippet announces CVE-2026-46513, outlining how Frogman allows headless PBX control through its HTTP API and mishandles API token storage, but it does not provide a PoC, exploit, or patch information.

    0000024
    92 followersView on X
  • CVE@CVEnew
    Disclosure

    CVE-2026-46513 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(r… https://www.cve.org/CVERecord?id=CVE-2026-46513

    Post summary

    The post outlines the technical flaw in Frogman’s token handling, but offers no PoC, exploit tool, active exploitation evidence, or patch information.

    00000600
    57.8K followersView on X

Explore more

Back to dashboard