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(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.
Scoring
- Severity
- HIGH
- CVSS base score
- 7.4
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- EPSS probability
- 0.43%
- CWE
- CWE-256
- Published
- 2026-07-16
- Last modified
- 2026-07-17
Affected products
- mwtcmi frogman
Weakness type
Related vulnerabilities
- CVE-2026-19051 — Plaintext Storage of User Credentials in Menulux Software's Menulux Portal
- CVE-2026-15933 — Cleartext Storage of Sensitive Credentials in OptimiDoc Server (On-Premise)
- CVE-2021-38489 — HDD Password Stored In Plaintext
- CVE-2026-82453 — rust-iot-platform Cleartext Password Storage via User Model
- CVE-2026-55765 — CloudNativePG: Cleartext role passwords recorded in pg_stat_statements allow privileged tenant roles to recover the PostgreSQL superuser credential and achieve RCE in the database pod
- CVE-2026-55164 — Lemur: Plaintext password storage in Lemur user-update path
- CVE-2026-50641 — Plaintext password storage in Streamsoft Business Intelligence
- CVE-2026-41874 — Hard-coded admin credentials in Quick.Cart