Frogman: API tokens stored in plaintext
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mwtcmi | frogman | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mwtcmi | Frogman |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.433% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mwtcmi
Mwtcmi frogman |
|
| Vendors & Products |
Mwtcmi
Mwtcmi frogman |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Frogman: API tokens stored in plaintext | |
| Weaknesses | CWE-256 | |
| References |
| |
| Metrics |
cvssV3_1
|